Eclipse Community Forums
Forum Search:

Search      Help    Register    Login    Home
Home » Eclipse Projects » Web Tools Project (WTP) » Editing JSP requires Tomcat restart
Editing JSP requires Tomcat restart [message #511022] Fri, 29 January 2010 10:04 Go to next message
Dominic is currently offline Dominic
Messages: 1
Registered: January 2010
Junior Member
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.

Report message to a moderator

Re: Editing JSP requires Tomcat restart [message #511060 is a reply to message #511022] Fri, 29 January 2010 06:34 Go to previous messageGo to next message
Larry Isaacs is currently offline Larry Isaacs
Messages: 1261
Registered: July 2009
Senior Member
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

Report message to a moderator

Re: Editing JSP requires Tomcat restart [message #511379 is a reply to message #511022] Mon, 01 February 2010 08:28 Go to previous messageGo to next message
Mauro Molinari is currently offline Mauro Molinari
Messages: 277
Registered: July 2009
Senior Member
Il 29/01/2010 16.04, void_kill@yahoo.co.uk ha scritto:
> Any ideas?

Is your project buildpath ok?

Mauro.

Report message to a moderator

Re: Editing JSP requires Tomcat restart [message #511565 is a reply to message #511022] Mon, 01 February 2010 23:04 Go to previous messageGo to next message
Sarika Sinha is currently offline Sarika Sinha
Messages: 38
Registered: February 2010
Location: Bangalore, India
Member
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.

Sarika Sinha
WTP Programmer
Source Editing

Report message to a moderator

Re: Editing JSP requires Tomcat restart [message #511696 is a reply to message #511565] Tue, 02 February 2010 05:00 Go to previous message
Larry Isaacs is currently offline Larry Isaacs
Messages: 1261
Registered: July 2009
Senior Member
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

Report message to a moderator

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

[ Syndicate this forum (XML) ] [ RSS ]

Current Time: Wed May 22 00:54:42 EDT 2013

Powered by FUDForum. Page generated in 0.11415 seconds