9.15.3 Setting the invocation order for servlets and JSPs
You set the invocation order for a WAR that contains servlets or JSPs.
- Organization of this subsection
(1) Attribute file to be edited
WAR attribute file
(2) Acquiring the attribute file to be edited and setting the attributes
-
Acquiring the attribute file
Execute the following command to acquire the following WAR attribute file:
- Execution format
cjgetappprop [server-name] [-nameserver provider-URL] -name J2EE application-name -type war -resname WAR-display-name -c path-of-the-WAR-attribute-file
- Example of execution
cjgetappprop MyServer -name account -type war -resname account_war -c C:\home\account_war.xml
-
Setting the attributes
Execute the following command to apply the values of the WAR attribute file:
- Execution format
cjsetappprop [server-name] [-nameserver provider-URL] -name J2EE application-name -type war -resname WAR-display-name -c path-of-the-WAR-attribute-file
- Example of execution
cjsetappprop MyServer -name account -type war -resname account_war -c C:\home\account_war.xml
(3) Attribute settings to be edited
The following table describes the invocation order settings for a WAR that contains servlets and JSPs:
|
Item |
Mandatory |
Corresponding tag |
|---|---|---|
|
Start and stop order# |
O |
<start-order> |
- Legend:
-
O: Optional
- #
-
The smaller the value, the earlier the application will start and larger the value, the earlier the application will stop. Note that if you specify the same value for servlets and JSPs, the invocation order between servlets and JSPs may not be as desired.
For details on the property settings, see 3.7.1 Specifications of the HITACHI WAR Property file in the uCosminexus Application Server Application and Resource Definition Reference Guide.