I had similar issues with my portlets.
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.


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]



Reply via email to