portals-jetspeed-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Randy Watler <rwat...@finali.com>
Subject RE: JS2 deployment
Date Fri, 21 Jan 2005 08:34:07 GMT

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

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.

- 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?

I will ponder more while I get some sleep...


-----Original Message-----
From: David Sean Taylor
To: Jetspeed Developers List
Sent: 1/18/05 1:55 PM
Subject: JS2 deployment


Since you are working on deployment issues, thought I share this with

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
[office] +01 707 773-4646
[mobile] +01 707 529 9194

To unsubscribe, e-mail: jetspeed-dev-unsubscribe@jakarta.apache.org
For additional commands, e-mail: jetspeed-dev-help@jakarta.apache.org

  • Unnamed multipart/alternative (inline, None, 0 bytes)
View raw message