Eclipse Community Forums
Forum Search:

Search      Help    Register    Login    Home
Home » Eclipse Projects » Web Tools Project (WTP) » Tomcat redeploys web application when a JSP get changed (because of faceted project dependencies are
Tomcat redeploys web application when a JSP get changed (because of faceted project dependencies are [message #222642] Tue, 14 October 2008 06:16 Go to next message
Mohsen Saboorian is currently offline Mohsen Saboorian
Messages: 19
Registered: July 2009
Junior Member
I think I found where the issue come from, but still no workaround.

I have two projects, one is a simple Java project which performs DBMS data
access (say p1), and another web module (say p2). Not all of my .jar files
are copied in the WEB-INF/lib of p2 (webmodule) project, but they are
actually referenced through "Java EE Module Dependencies", so that Eclipse
copies p1 and p2 projects' dependencies to the target module deployment
folder's WEB-INF/lib.

p1 project has Utility Module facet, so that whenever it changes a new jar
file is created and exported to p2's WEB-INF/lib. The problem is that
whenever I change a simple .jsp page (in p2), a new p1.jar is created in
WEB-INF/lib and this is the cause that Tomcat reloads the module.

There is also another issue which I believe happens because of another facet
set in my p1 project. I have eclipselink.jar as a dependency in my pure java
project (p1). There is also a JPA facet set in p1 project. Whenever I change
a jsp, not only p1.jar is modified, but also eclipselink.jar is re-copied in
WEB-INF/lib.

Isn't it a bug in WTP facet engine?

Thanks,
Mohsen.
Re: Tomcat redeploys web application when a JSP get changed (because of faceted project dependencies [message #222663 is a reply to message #222642] Thu, 16 October 2008 06:36 Go to previous message
Eclipse User
Originally posted by: mohsen.siahe.com

Reported as bug 250966.

"Mohsen Saboorian" <mohsens@gmail.com> wrote in message
news:gd1dqe$o8v$1@build.eclipse.org...
>I think I found where the issue come from, but still no workaround.
>
> I have two projects, one is a simple Java project which performs DBMS data
> access (say p1), and another web module (say p2). Not all of my .jar files
> are copied in the WEB-INF/lib of p2 (webmodule) project, but they are
> actually referenced through "Java EE Module Dependencies", so that Eclipse
> copies p1 and p2 projects' dependencies to the target module deployment
> folder's WEB-INF/lib.
>
> p1 project has Utility Module facet, so that whenever it changes a new jar
> file is created and exported to p2's WEB-INF/lib. The problem is that
> whenever I change a simple .jsp page (in p2), a new p1.jar is created in
> WEB-INF/lib and this is the cause that Tomcat reloads the module.
>
> There is also another issue which I believe happens because of another
> facet
> set in my p1 project. I have eclipselink.jar as a dependency in my pure
> java
> project (p1). There is also a JPA facet set in p1 project. Whenever I
> change
> a jsp, not only p1.jar is modified, but also eclipselink.jar is re-copied
> in
> WEB-INF/lib.
>
> Isn't it a bug in WTP facet engine?
>
> Thanks,
> Mohsen.
>
Previous Topic:Where do I find WTP Updates for Ganymede?
Next Topic:maven, eclipse, WTP 1.5.5 and deep project structures
Goto Forum:
  


Current Time: Thu Oct 23 09:02:45 GMT 2014

Powered by FUDForum. Page generated in 0.07681 seconds
.:: Contact :: Home ::.

Powered by: FUDforum 3.0.2.
Copyright ©2001-2010 FUDforum Bulletin Board Software