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