Eclipse Community Forums: ServerTools (WTP) » Editing JSP requires Tomcat restart

Home » Language IDEs » ServerTools (WTP) » Editing JSP requires Tomcat restart

Editing JSP requires Tomcat restart [message #511022]

Fri, 29 January 2010 10:04

Eclipse User

This has started sometime recently that whenever I edit a JSP page the server entry shows "Debugging, Restart" as it's status, when previously the JSP files could be updated without needing to restart.

I haven't installed any new plugins.
Eclipse JEE Galileo with WTP JEE tools shows v3.1.1

Any ideas?

Thanks, Dominic.

Re: Editing JSP requires Tomcat restart [message #511060 is a reply to message #511022]

Fri, 29 January 2010 06:34

Eclipse User

void_kill@yahoo.co.uk wrote:
> This has started sometime recently that whenever I edit a JSP page the
> server entry shows "Debugging, Restart" as it's status, when previously
> the JSP files could be updated without needing to restart.
>
> I haven't installed any new plugins.
> Eclipse JEE Galileo with WTP JEE tools shows v3.1.1
>
> Any ideas?
>
> Thanks, Dominic.

Usually, this behavior implies something in addition to the JSP got
"published". Is reloading still enabled (the default) for the Tomcat
Context for that project? If so, does the Tomcat log show evidence that
that Context reloaded? If it reloaded, that would imply that the jar
for a dependent Java project got rebuilt and published. As far as I
know, all the bugs that led to this behavior in prior versions of WT{
have been fixed.

A test with a simple Dynamic Web Project doesn't show this behavior for
me. I would need to know more details about the project and its
dependencies and how Tomcat is configured (any changes from the
defaults) to speculate further.

Cheers,
Larry

Re: Editing JSP requires Tomcat restart [message #511379 is a reply to message #511022]

Mon, 01 February 2010 08:28

Eclipse User

Il 29/01/2010 16.04, void_kill@yahoo.co.uk ha scritto:
> Any ideas?

Is your project buildpath ok?

Mauro.

Re: Editing JSP requires Tomcat restart [message #511565 is a reply to message #511022]

Mon, 01 February 2010 23:04

Eclipse User

This can happen if the Server properties are set in auto publish mode. You can right click on server instance and open to verify if the "Auto Publish" is on? If it's on you can switch this off. This will stop the auto publishing after each change in jsp. Only when you say run on server it will be published.

Re: Editing JSP requires Tomcat restart [message #511696 is a reply to message #511565]

Tue, 02 February 2010 05:00

Eclipse User

Sarika Sinha wrote:
> This can happen if the Server properties are set in auto publish mode.
> You can right click on server instance and open to verify if the "Auto
> Publish" is on? If it's on you can switch this off. This will stop the
> auto publishing after each change in jsp. Only when you say run on
> server it will be published.

Changing just a JSP should not cause the Tomcat server to request a
restart, auto publish or not. It it does, it implies something else is
getting re-published along with the JSP, which may be unnecessary if
only the JSP changed. An effort has been made to avoid such
"re-publishes", when possible. As far as I know, all such
"re-publishes" have been addressed and fixed. However, if you are
seeing this behavior in the latest WTP, then we may have a bug. There
could be a new "re-publish" we need to address or an old "re-publish"
that inadvertently got un-fixed. To address, we would need to track
down exactly what it is in the projects involved that is triggering the
unnecessary "re-publish".

Cheers,
Larry

Previous Topic:	Is WTP built-in in Eclipse since v3.5 ? Version of subprojects?
Next Topic:	WTP 3.2 M5 Failure

Goto Forum:

-=] Back to Top [=-

Current Time: Wed Jul 23 13:26:59 EDT 2025

.:: Contact :: Home ::.

Breadcrumbs

Sign up to our Newsletter