使用Eclipse和Tomcat（Servlet 3.0）在Web片段中热部署JSP

Question

I have a project set up like this:

/parent
 /core
  /src/main/
   /resources/META-INF/
      web-fragment.xml
      /resources/jsp/
        fragment.jsp
   /java/
     FragmentTest.java
 /web
  /src/main/
    /webapp/
      /WEB-INF/web.xml
      /jsps/
        parent.jsp
    /java/
      ParentTest.java

the 'core' compiles to a .jar within the .war.

However, when deploying this to Tomcat, with debug enabled, I can edit parent.jsp and it will hot deploy, however if I update fragment.jsp then it will not, and I have to rebuild/redeploy/etc.

However, any changes to the .java in either project will hot-deploy successfully.

Is anyone aware of any configurations, etc. that may be missing to get web-fragment JSPs to hot deploy?

Thanks!

Answer 1

I have the same situation. I have test-web (your parent ) and test-web-fragment (your core ). I resolved them in the following way:

In the /test-web -> Properties -> Deployment Assembly I added the Fileset rule that points to /test-web-fragment/src/main/resources/META-INF/resources (See the screenshots below).

When I change something in a page from fragment, the eclipse builder copies it to /test-web/src/main/webapp . After that I do a right click to test-web in app server and click Full Publish and I have to the server my changes. This trick I use in the development mode. When I make the build for production I use maven, without this rule.

Answer 2

Your project structure confuses me a bit. We always place JSPs in /src/main/webapp and sub folders therein. I can very well imagine this to be the source of your problem.

Answer 3

You will be able to hot deploy both JSPs and Java files if you do the following:

Separate your web fragment project into two different projects and reference them from your main Web applications:

• One containing all your Java source files (this project has to be a Web Fragment). This will be packed as a JAR file and you will be able to hot deploy Java files as you're currently doing
• Another project, a Dynamic Web Project, containing all your static / JSP files under the WebContent folder. This will be deployed unpacked and will allow you to hot deploy everything under WebContent folder

There could be a better option than this one, but at least you will be able to work properly until you find something better.