Randy,
Since you are working on deployment issues, thought I share this with you.
We (Scott and I) would like to consider a new (old) method to deployment. This method would hook into the servlet init, and register the portlet application to Jetspeed during servlet initialization. If you set the app to init at startup, then your PA will get registered during app server startup.
This means that we will no longer need specific code for application deployment to each app server. In theory, this may solve our race condition issues.
Start with a look at the JetspeedContainerServlet in the commons directory. It has a "registerAtInit" init parameter.
I added this functionality a while back as a solution to register with Jetspeed during servlet init - so that we don't have to worry about deployment issues specific to app servers. In the long run the current method won out, but we are now reconsidering this method.
Finally, there is also a command line utility for registering portlet applications. See the deploy-tool component, and the uberjar goal
Give it a spin and let us know what you think,
-- 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]
