Randy Watler wrote:
David/Scott,
I like this solution... it is MUCH cleaner codewise than trying to deal with the various application servers/environments. I'll give it a try sometime tomorrow.
A few questions for the uninformed:
- I am assuming that the various portlet apps would never actually invoke
the JetspeedContainerServlet... is that right? If so, perhaps it would be
better to use a listener/ServletContextListener hook: this might be easier
to infuse in the web.xml.
I like the listener/ServletContextListner idea.
I would like to see it work like this:- All of this works because Jetspeed-commons resides in a shared class loader, right? Is that functionality part of the Servlet Container spec... must be, no?
- Are you imagining this as strictly a build time tool or are you thinking
we could encorporate the logic in the deploy-tool to the existing File based
PAM and deploy complete war files into webapps at runtime?
1. Run and "infusing" deploy tool that all it does is mod the web.xml and add the correct entries for the J2 servlets.
2. Leave it up to the user to deploy the newly infused war to the container of their choice.
3. When app sucessfuly deploys, the listener/servlet (which ever the choice is) does the registeration.
I will ponder more while I get some sleep...
Randy
-----Original Message----- From: David Sean Taylor To: Jetspeed Developers List Sent: 1/18/05 1:55 PM Subject: JS2 deployment
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,
-- "Great minds discuss ideas. Average minds discuss events. Small minds discuss people." - Admiral Hyman Rickover
******************************************* * Scott T. Weaver * * <[EMAIL PROTECTED]> * * <http://www.einnovation.com> * * -------------------------------------- * * Apache Jetspeed Enterprise Portal * * Apache Pluto Portlet Container * * * * OpenEdit, Website Content Management * * <http://www.openedit.org> * *******************************************
--------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
