
|
If you were logged in you would be able to see more operations.
|
|
|
Spring OSGi
Created: 16/Jun/08 09:45 AM
Updated: Saturday 01:55 PM
|
|
| Component/s: |
WEB
|
| Affects Version/s: |
1.1 M2
|
| Fix Version/s: |
1.2 M2
|
|
|
Environment:
|
Tomcat 5.5 with Spring DM 1.1 M2
Tomcat 5.5 with Spring DM 1.1 M2
|
|
|
Currently the Tomcat WAR deployer deploys the WAR bundle to a temp file location under the user's home directory (e.g. tomcat-notifServResources7169.osgi). This makes running this type of bundle in a controlled environment where sys admins will balk at such deployments impossible to manage.
The createDocBase method in the TomcatWarDeployer class is private and fairly hard coded.
A strategy class that could be injected (in a similar fashion as the ContextPathStrategy) would be an ideal way to provide customization of this (e.g. a TomcatDocBaseStrategy), the default strategy could be the logic in the current private createDocBase method.
|
|
Description
|
Currently the Tomcat WAR deployer deploys the WAR bundle to a temp file location under the user's home directory (e.g. tomcat-notifServResources7169.osgi). This makes running this type of bundle in a controlled environment where sys admins will balk at such deployments impossible to manage.
The createDocBase method in the TomcatWarDeployer class is private and fairly hard coded.
A strategy class that could be injected (in a similar fashion as the ContextPathStrategy) would be an ideal way to provide customization of this (e.g. a TomcatDocBaseStrategy), the default strategy could be the logic in the current private createDocBase method. |
Show » |
| There are no comments yet on this issue.
|
|