[news.eclipse.webtools] Re: Building Working Set

[Larry Isaacs <Larry.Isaacs@xxxxxxx>]

breako wrote:
> Hi,
> I am using ganymede with Tomcat 5.5.
> I make changes to a single class which has no dependencies on any other 
> class.
> I have build automatically disabled.  I create a build working set, 
> which only contains this class.
>
> I select to build the working set.
>
> My tomcat server restarts and the new version class is in the classloader.

I assume that the whole server doesn't restart, but that the context for 
the webapp in question reloads.

> I would like for my tomcat server to not have to restart.
> Any ideas?

That depends on whether you want your class changes visible.  If not, 
then you can either turn off auto-reloading for that context, or turn 
off auto-publishing for the server and manually publish to make changes 
visible.  The first approach would not affect JSP changes being quickly 
visible.  The second approach would require a manual publishing for JSP 
changes as well as class changes to become visible.

After manually publishing class changes, the Servers view will say that 
Tomcat needs to restart.  However, if the automatic reload is 
successful, you can keep going.  Note that "reloading" can be quirky 
depending on the changes you make and often leaks the old context's 
classloader, which will eventually lead to OutOfMemoryErrors.

Cheers,
Larry

> Thanks.