Eclipse Community Forums: ServerTools (WTP) » Debug servlet with Tomcat require restart after each modification

Help

Home

Home » Language IDEs » ServerTools (WTP) » Debug servlet with Tomcat require restart after each modification

Show: Today's Messages :: Show Polls :: Message Navigator

Debug servlet with Tomcat require restart after each modification [message #151839]

Wed, 14 December 2005 07:12

Eclipse User

Originally posted by: whisk_whisk.yahoo.com

Hi all,

I am now using the eclipse 3.1.1, WTP 1.0RC4, and Tomcat 5.0 as my
development platform.

The Tomcat is started in debug mode and all break points are stopped
successfully.

However, everytime I have modified a servlet, even just adding a blank
space, triggers a restart of the Tomcat server.

What I expect is the hotswap of the classes with no structual change. How
should I configure the Eclipse and Tomcat to achieve this?

Thank you very much for your help!

Best wishes,

WHiSK

Report message to a moderator

Re: Debug servlet with Tomcat require restart after each modification [message #152252 is a reply to message #151839]

Wed, 14 December 2005 12:48

Eclipse User

Originally posted by: dserodio.gmail.com

WHiSK wrote:
> Hi all,
>
> I am now using the eclipse 3.1.1, WTP 1.0RC4, and Tomcat 5.0 as my
> development platform.
>
> The Tomcat is started in debug mode and all break points are stopped
> successfully.
>
> However, everytime I have modified a servlet, even just adding a blank
> space, triggers a restart of the Tomcat server.
>
> What I expect is the hotswap of the classes with no structual change.
> How should I configure the Eclipse and Tomcat to achieve this?

I expect that too, if the "Tomcat Plugin" can do it, why can't WTP?

TIA,
Daniel Serodio

Report message to a moderator

Re: Debug servlet with Tomcat require restart after each modification [message #152267 is a reply to message #151839]

Wed, 14 December 2005 14:04

Nitin Dahyabhai

Messages: 4435
Registered: July 2009

Senior Member

WHiSK wrote:
> I am now using the eclipse 3.1.1, WTP 1.0RC4, and Tomcat 5.0 as my
> development platform.
>
> The Tomcat is started in debug mode and all break points are stopped
> successfully.
>
> However, everytime I have modified a servlet, even just adding a blank
> space, triggers a restart of the Tomcat server.
>
> What I expect is the hotswap of the classes with no structual change.
> How should I configure the Eclipse and Tomcat to achieve this?

You mean an actual Servlet class? You might want to open a bug if
you're seeing this and Sysdeo's plugin handles it better.

--
- Nitin

_
Nitin Dahyabhai
Eclipse Web Tools Platform

Report message to a moderator

Re: Debug servlet with Tomcat require restart after each modification [message #152317 is a reply to message #152252]

Wed, 14 December 2005 16:05

Eclipse User

Originally posted by: whisk_whisk.yahoo.com

Daniel Serodio wrote:

> WHiSK wrote:
>> Hi all,
>>
>> I am now using the eclipse 3.1.1, WTP 1.0RC4, and Tomcat 5.0 as my
>> development platform.
>>
>> The Tomcat is started in debug mode and all break points are stopped
>> successfully.
>>
>> However, everytime I have modified a servlet, even just adding a blank
>> space, triggers a restart of the Tomcat server.
>>
>> What I expect is the hotswap of the classes with no structual change.
>> How should I configure the Eclipse and Tomcat to achieve this?

> I expect that too, if the "Tomcat Plugin" can do it, why can't WTP?

> TIA,
> Daniel Serodio

This is really strange! Is there any config trick to make hotswap
possible?
I prefer a simple startup rather than those complicated remote debugging.

Report message to a moderator

Re: Debug servlet with Tomcat require restart after each modification [message #152323 is a reply to message #152267]

Wed, 14 December 2005 16:08

Eclipse User

Originally posted by: whisk_whisk.yahoo.com

Nitin Dahyabhai wrote:

> WHiSK wrote:
>> I am now using the eclipse 3.1.1, WTP 1.0RC4, and Tomcat 5.0 as my
>> development platform.
>>
>> The Tomcat is started in debug mode and all break points are stopped
>> successfully.
>>
>> However, everytime I have modified a servlet, even just adding a blank
>> space, triggers a restart of the Tomcat server.
>>
>> What I expect is the hotswap of the classes with no structual change.
>> How should I configure the Eclipse and Tomcat to achieve this?

> You mean an actual Servlet class? You might want to open a bug if
> you're seeing this and Sysdeo's plugin handles it better.

yup... a Servlet class, or even a HTML page change will trigger a restart.
I tried Sysdeo's plugin but the settings are not user friendly, and seems
do not support multiple server.

May I ask one more question? Is this just happen on wtp with tomcat? how
about wtp with websphere?

Thanks all!

Report message to a moderator

Re: Debug servlet with Tomcat require restart after each modification [message #152337 is a reply to message #152317]

Wed, 14 December 2005 19:55

Darryl Miles

Messages: 123
Registered: July 2009

Senior Member

WHiSK wrote:
> This is really strange! Is there any config trick to make hotswap
> possible? I prefer a simple startup rather than those complicated remote
> debugging.

Point 1) The Hot-swap part is standard with Sun JDK 1.5 just launch the
runtime in debug mode.

Point 2) Now to stop Tomcat reloading the servlet one config trick maybe
to have a file:

WebContent/META-INF/context.xml:

and in that file might be something like this:

---- SNIP ----
<?xml version="1.0" encoding="UTF-8"?>
<Context path="/mycontext"
debug="1"
reloadable="false">
<Parameter name="runtimeEnvironment" value="DEVEL" override="false"/>

</Context>
---- SNIP ----

Note the reloadable="false" this tells Tomcat that changes inside the
WEB-INF/classes hierachy are not to auto-re-deploy the web-app.

Point 3) Now if you are saying that the Tomcat Server Runtime driver is
forcing a reload you'll need to open a bug for since thats certainly not
necessary in all^H^H^Hmost situations.

But before opening the bug you need to be sure what you are seeing is a
forced reload by the Tomcat Server Runtime driver and not an
auto-re-reploy by tomcat itself because its operating as-if
reloadable="true".

I will upgrade WTP later and confirm Point 3 really isn't the case, I
did not get that feeling from RC3 or RC4, the development process was
really getting back that warm and fuzzy feeling I get inside.

Darryl

Report message to a moderator

Re: Debug servlet with Tomcat require restart after each modification [message #152632 is a reply to message #152337]

Fri, 16 December 2005 18:31

Eclipse User

Originally posted by: whisk_whisk.yahoo.com

Thank you very much!!!
the reloadable="false" is the key word of not to reload all the
servlets!!!!!!

or we can simple double click on the Server->Server
Configuration->Modules->Edit->Untick Auto Reloading Enabled

Once again, thank you all!

Report message to a moderator

Re: Debug servlet with Tomcat require restart after each modification [message #152648 is a reply to message #152632]

Fri, 16 December 2005 22:23

Darryl Miles

Messages: 123
Registered: July 2009

Senior Member

WHiSK wrote:
> or we can simple double click on the Server->Server
> Configuration->Modules->Edit->Untick Auto Reloading Enabled

You know I have completely forgotten that "Modules" tab exists. There
was another query open for changing the Context path for a WebModule.
This looks like the place in UI that should do the trick.

Darryl

Report message to a moderator

Re: Debug servlet with Tomcat require restart after each modification [message #152673 is a reply to message #152648]

Sat, 17 December 2005 06:03

Eclipse User

Originally posted by: whisk_whisk.yahoo.com

Darryl L. Miles wrote:

> WHiSK wrote:
>> or we can simple double click on the Server->Server
>> Configuration->Modules->Edit->Untick Auto Reloading Enabled

> You know I have completely forgotten that "Modules" tab exists. There
> was another query open for changing the Context path for a WebModule.
> This looks like the place in UI that should do the trick.

> Darryl

Yup~ exactly! but that tab can easily be ignored. the tab size should be
made bigger! it is toooo small now, i noticed it just by luck. >_<

happy programming!

Report message to a moderator

Previous Topic:	external jars
Next Topic:	IWAB0489E Error

Goto Forum:

-=] Back to Top [=-

[ Syndicate this forum (XML) ] [

]

Current Time: Thu Apr 25 04:01:11 GMT 2024

.:: Contact :: Home ::.

Breadcrumbs

Sign up to our Newsletter