David Sean Taylor wrote:
Christophe Lombart wrote:
I had similar issues with my portlets.I usually just deploy the entire webapp (portlet app) by dropping it into the jetspeed deploy directory (maven task), although that can be expensive if you have a lot jars in your distribution, but it still can be quicker than restarting
There is a bug in tomcat 5.0.28 with the autoDeploy. It is not used correctly in this version.
Now, I use tomcat 5.0.30 and hot deploy works fine.
I still think we need to further look into Jetspeed portlet cache since it holds on to the webapp class loader and could be causing this kind of problem. Not sure if Ate's latest go at deployment is considering this or not
yes ;-) The main rationale behind my refactoring is relying on the web server classloader handling only (for non-local portlet applications).
Christophe
Howard Lewis Ship wrote:
Is there a quick and easy way to force Jetspeed to restart?
I'm hot deploying a small portlet into Jetspeed.
I believe (not 100% certain) that it is picking up changes to my Portlet instance after the hot deploy.
It does not appear to pick up changes to a static helper class. I see
Portlet is Not Available: ClickLink Reason: Node has been removed.
At the bottom of my portlet's window.
I'm having to stop/restart Tomcat to pick up such changes and I'm hoping for something a little quicker and easier.
--------------------------------------------------------------------- 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]
