Re: Force restart/reload
On Thu, 24 Feb 2005 23:10:48 -0500, Craig Doremus [EMAIL PROTECTED] wrote: Hi, This is somewhat off topic, but of interest to us in 'portal-land': Are you working on making Tapestry JSR-168 compatible? If not, do you have plans to move in this direction? That's exactly what I'm working on right now. Tapestry 3.1 will have an add-on library that turns Tapestry into a natively portlet compliant framework. I'm introducing a number of abstractions to deal with the differences -- Howard M. Lewis Ship Independent J2EE / Open-Source Java Consultant Creator, Jakarta Tapestry Creator, Jakarta HiveMind Professional Tapestry training, mentoring, support and project work. http://howardlewisship.com - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Force restart/reload
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. -- Howard M. Lewis Ship Independent J2EE / Open-Source Java Consultant Creator, Jakarta Tapestry Creator, Jakarta HiveMind Professional Tapestry training, mentoring, support and project work. http://howardlewisship.com - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Force restart/reload
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]
Re: Force restart/reload
Christophe Lombart wrote: 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. 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 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 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] -- David Sean Taylor Bluesunrise Software [EMAIL PROTECTED] [office] +01 707 773-4646 [mobile] +01 707 529 9194 - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Force restart/reload
David Sean Taylor wrote: Christophe Lombart wrote: 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. 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 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]
Re: Force restart/reload
Hi, This is somewhat off topic, but of interest to us in 'portal-land': Are you working on making Tapestry JSR-168 compatible? If not, do you have plans to move in this direction? TIA /Craig 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]
