Eclipse Community Forums: ServerTools (WTP) » JSP/XHTML on classpath triggers Tomcat Restart

Help

Home

Home » Language IDEs » ServerTools (WTP) » JSP/XHTML on classpath triggers Tomcat Restart

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

JSP/XHTML on classpath triggers Tomcat Restart [message #642056]

Mon, 29 November 2010 17:17

Tserb

Messages: 3
Registered: November 2010

Junior Member

Hi all,

our WTP project is setup the way that xhtml files are to be found on the classpath. However in this case, if we publish to Tomcat, then it always wants to restart. This was not the case when XHTML files were not on the classpath.
How can I configure WTP/Tomcat to avoid this?

Thank you!

Report message to a moderator

Re: JSP/XHTML on classpath triggers Tomcat Restart [message #645787 is a reply to message #642056]

Mon, 20 December 2010 15:23

Tserb

Messages: 3
Registered: November 2010

Junior Member

BUMP.

Is there really nobody who could help with this?

Report message to a moderator

Re: JSP/XHTML on classpath triggers Tomcat Restart [message #645993 is a reply to message #645787]

Tue, 21 December 2010 13:46

Larry Isaacs

Messages: 1354
Registered: July 2009

Senior Member

On 12/20/2010 10:23 AM, Tserb wrote:
> BUMP.
>
> Is there really nobody who could help with this?

The handling of classpath resources doesn't try to distinguish classes
from other resources and assumes any change requires a restart. You can
ignore the restart if you know the changed resource doesn't need a
restart to be served after publishing.

Cheers,
Larry

Report message to a moderator

Re: JSP/XHTML on classpath triggers Tomcat Restart [message #646059 is a reply to message #642056]

Tue, 21 December 2010 18:37

Trung Nguyen

Messages: 4
Registered: December 2010

Junior Member

Does your XHTML exist outside of the main webapp project, like in another dependent project? If so, eclipse will rebuild that project's jar and that needs a redeploy.

Report message to a moderator