Try this setting: services.PortletFactory.enable.cache=false
Not recommended for production, since it will reload your portlet classes with every request > -----Original Message----- > From: George Clernon [mailto:[EMAIL PROTECTED]] > Sent: Wednesday, March 27, 2002 10:36 AM > To: Jetspeed Users List > Subject: Re: Portlet development... > > > > If a context is reloadable tomcat will reload the changed classes > automatically: > > <Context path="/jetspeed" docBase="jetspeed" > reloadable="true"/> > > $TOMCAT_HOME/conf/server.xml > > I tried it for jetspeed without success but it works great for other > turbine based apps. > > > -George Clernon. > > > On Wednesday 27 March 2002 18:21, you wrote: > > Julia, > > I assume you are changing you portlet java source code. If you are > > using Tomcat 4.x, you MAY be able to user Tomcat's manager > webapp to > > reload jetspeed, i.e. > http://localhost/manager/reload?> path=/jetspeed. > > I tried > this along time ago, but it did > not work because the user > > database as locked. > > > > Paul Spencer > > > > Julia A. Case wrote: > > > Last question for a while (I promise) > > > > > > I've developed 3 portlets this week. But, right now I have to > > > shutdown and restart the tomcat server to get a changed > portlet to > > > take affect. This cuts into the development time waiting for the > > > server to cycle. Is there a better way? I tried setting > > > isCacheable to false but that didn't help. > > > > > > Thanks, > > > Julia > > -- > To unsubscribe, e-mail: > <mailto:jetspeed-user-> [EMAIL PROTECTED]> > For > additional commands, > e-mail: <mailto:[EMAIL PROTECTED]> > > -- To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]> For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>
