Jetspeed 2 supports hot deploy. You just drop a war file into the deployment directory and to portlet is deployed. Also, deleting the war while the container is in operation will automatically undeploy that portlet application.
This capability is still in the early stages of development and there appears to be some issues when undeploying then redpolying the web application into Tomcat. When this is done, tomcat returns a null RequestDispatcher within the redeployed portlet applications. Regards, *================================* | Scott T Weaver | | <[EMAIL PROTECTED]> | | Apache Jetspeed Portal Project | | Apache Pluto Portlet Container | *================================* > -----Original Message----- > From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] > Sent: Tuesday, January 20, 2004 7:13 AM > To: Jetspeed Users List > Subject: No real way to deploy portlets? > > Sorry if this question is missing something huge. I'm investigating > several portal frameworks, and with Jetspeed, I cannot find > any production orientated way to deploy portlets.. > By this I mean excluding having to restart Tomcat, which is not really > an option in any normal operating environment. > I've seen some vague references in mailing lists to hot class loading, > so I'm assuming this is a close as I'll get? > Specifically is there any support, planned or existing, for deploying > portlets as war, ear or jar files? > > > Many thanks. > WH > > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
