If you are concerned with class-based portlets, you can define your webapp's context as reloadable="true" in the server.xml file. By default, there is no context entry for Jetspeed in server.xml, so you will have to define it yourself. However, I am not 100% sure this will work for new classes (i.e. those that were not there when the webapp's classloader first initialized). What will work is using Tomcat's manager functionality to forcibly re-load the webapp. There is a catch to this approach. If you are using the default HSQL as your database, you will get a "Database already in use" error after the webapp reloads. I got around this by moving to MySQL. There may be other ways to prevent HSQL from behaving this way, however I did not want to spend the time to figure it out. As for the required .xreg entries, AFAIK those refresh every so often. hth, Scott > -----Original Message----- > From: Bui Quoc Thai [mailto:[EMAIL PROTECTED]] > Sent: Wednesday, June 26, 2002 4:39 AM > To: Jetspeed Developers List > Subject: deploy a portlet without restarting Tomcat > > Hi, > > I'm using jetspeed Portal 1.3a2 and Tomcat 4.0.1. How can I deploy a new > portlet without restarting the Tomcat. > Thanks for your help. > > Thai > > > ---------------------------------------------------------- > This mail sent through AIT WebMail : http://www.ait.ac.th/ > > -- > To unsubscribe, e-mail: <mailto:jetspeed-dev- > [EMAIL PROTECTED]> > For additional commands, e-mail: <mailto:jetspeed-dev- > [EMAIL PROTECTED]>
