I'd like to point out an alternative solution that is available today in Fusion.
For deployment:
1. Deploy the application to your application server as you would normally
2. Use the Fusion JSR-168 Portlet Application Admin portlet to register the application by context name.
For undeployment:
1. De-register the applicaton with the Fusion JSR-168 Portlet Application Admin portlet.
2. Use your app server specific method to remove the application.
In Fusion, there is a secondary method of deployment that doesn't require a user interface. Again, this method has already been written and tested. If a PA's web.xml has a 'registerAtInit' init param, the Jetspeed Container will:
1. register new portlet apps during servlet init
2. for existing portlet apps, use a checksum on the PA to see if its been modified. (the checksum is stored in the PORTLET_APPLICATION table). if the app has changed, redeploy
This solution requires running a command line utility See the components/deploy-tool for infusing the webapp:
To Run the command line tool to simply infuse the Jetspeed Container:
java -jar target/jetspeed-deploy-tools-2.0-M1-uber.jar source.war destination.war
To make a portlet application register at Servlet init time:
java -jar target/jetspeed-deploy-tools-2.0-M1-uber.jar -r source.war destination.war
Again, just wanted to point out that this solution already exists and is used successfully with Weblogic, JBoss and Wepshere as well as Tomcat.
Im -1 on un-registering with every shutdown of the server.
-- David Sean Taylor Bluesunrise Software [EMAIL PROTECTED] [office] +01 707 773-4646 [mobile] +01 707 529 9194
--------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
