WebApp Component Reference

Field Description
WTP Project

Start with the Eclipse WTP project containing the WebApp component implementation. Alternatively, you can create a new WTP project from the generate servlet implementation.

WAR Start with the WAR file containing the WebApp component implementation.
Plugin Project Creates a plugin project implementation.

Compute Feature Dependencies

Properties

The Context Root and Connector Name properties must always be set.
Field Description
contextRoot

The context root of a web application determines which URLs are to be delegated to your web application. If your application's context root is myapp, any request for /myapp or /myapp/* are handled. For example, http://localhost:8080/myapp/index.html.

NOTE:

  • A WebApp component must have a unique context root.
  • The contextRoot property must have only one element.
defaultConnector

This property defines the name for an HTTP Inbound connector. For a Web application, a browser is only way of communication and as browser uses HTTP to communicate with any Web application. In TIBCO ActiveMatrix, you need to configure this HttpInbound Resource template in Administrator before deploying a Web application.

Field Description
Compute Feature Dependencies Indicate whether to compute the features on which the component bundle depends. When unchecked, the Feature Dependencies table displays.
Default:
  • New projects - selected.
  • Legacy projects - cleared.
Preview Displays a dialog containing a list of features on which the component bundle depends.

Features Dependencies

Column Description
Feature ID ID of the feature.
Version Range Range of feature versions.
By default, the table lists the details of the automatically-generated feature containing the component implementation bundle.

Plugin Project

Field Description
Plugin Project Selected plugin project implementation.
Deployment Descriptor (web.xml) File

Location of the web.xml file.

Thread Context Class Loader Type Configures the Thread Context Class Loader property:
  • component - The class loader of the component bundle. The class loader has visibility to the component bundle class path space, Import-Package, and Require-Bundle entries from the component.
  • bundle - The class loader of the implementation bundle. The class loader has visibility to the bundle class path space and the Class-Space because of entries in the MANIFEST.MF file.
  • none - A null thread context class loader.

Default: component

Package the Implementation Bundle with the Application

Field Description
Package the implementation bundle with the application Indicate whether to compute the component bundle dependencies. When a component is deployed on a node, ActiveMatrix generates a component bundle. When selected, the component implementation bundles required by the component bundle are computed and identified when you package the composite. When cleared, the Implementation Dependency and Compute Feature Dependencies fields display and you can manually specify the dependencies.
Default:
  • New projects - selected.
  • Legacy projects - cleared.
Implementation Dependency Type of the dependency of the component bundle on the component implementation.
  • Require Bundle - The bundle containing the component implementation is declared as a required bundle. When selected, the Bundle Name field displays.

Default: Require Bundle

Bundle Name Symbolic name of the bundle containing the component implementation.

Default: The bundle in which the component implementation class is present.

Package Name Name of the package containing the component implementation.

Default: The package in which the component implementation class is present.

Version Range Versions of the bundle or package that satisfy the component bundle's dependency. When specifying a range for a bundle, you may require an exact match to a version that includes a build qualifier. In contrast, the range for a package is inexact.
Default:
  • Bundle - [1.0.0.qualifier,1.0.0.qualifier].
  • Package - [1.0.0, 2.0.0).