[jira] Issue Comment Edited: (IVYDE-226) JSP change causes context refresh (entire WAR restarts) - IvyDE EE Module dependency copies all jars to tomcat directory even if unchanged

["Jon Schneider (JIRA)" <ji...@apache.org>]

    [ https://issues.apache.org/jira/browse/IVYDE-226?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12790184#action_12790184 ] 

Jon Schneider edited comment on IVYDE-226 at 1/5/10 1:53 PM:
-------------------------------------------------------------

After playing around with this for a little while, I've made the following observations that appear to be different from what you are reporting:

1.  After changing a JSP that is in the WEB-INF folder, the server changes status from "Started, Synchronized" to "Started, Restart".  On restart, of course, the server is synchronized again.  I have not observed the jars being recopied at this point (this is where I expected to see the problem, since I am fiddling with the WEB-INF folder and I've noticed some server adapters are sensitive about that).

2.  After changing a JSP that is NOT in the WEB-INF folder, say in the WebContent root, the server remains synchronized after the file modification.  Again, I do not observe jars being recopied to the deployed directory after the initial publish.

I tested this with a barebones Dynamic Web project with one Ivy classpath container and a single JSP on Tomcat 6.0.20.

Perhaps you could provide a test project?

Thanks,
Jon

      was (Author: jkschneider):
    After playing around with this for a little while, I've made the following observations that appear to be different from what you are reporting:

1.  After changing a JSP that is in the WEB-INF folder, the server changes status from "Started, Synchronized" to "Started, Restart".  On restart, of course, the server is synchronized again.  I have not observed the jars being recopied at this point.

2.  After changing a JSP that is NOT in the WEB-INF folder, say in the WebContent root, the server remains synchronized after the file modification.  Again, I do not observe jars being recopied to the deployed directory after the initial publish.

I tested this with a barebones Dynamic Web project with one Ivy classpath container and a single JSP on Tomcat 6.0.20.

Perhaps you could provide a test project?

Thanks,
Jon
  
> JSP change causes context refresh (entire WAR restarts) - IvyDE EE Module dependency copies all jars to tomcat directory even if unchanged
> ------------------------------------------------------------------------------------------------------------------------------------------
>
>                 Key: IVYDE-226
>                 URL: https://issues.apache.org/jira/browse/IVYDE-226
>             Project: IvyDE
>          Issue Type: Bug
>    Affects Versions: 2.1.0
>         Environment: Windows WTP Galileo & Tomcat 6
> IvyDE 2.1.0-hudson-79
>            Reporter: Dave
>
> Problem: If I make a JSP only change in a Web project causes the entire web application context to restart in Tomcat 6.  Due to legacy application design, restart takes several minutes.
> Configuration:
> Web project has a IvyDE classpath dependency.  This dependency is marked as a Java EE module dependency.  Build Automatically is on.
> Investigation:
> Change to JSP causes project build, the project build exports the dependent jars to the WTP server folder:
> wtpwebapps\MyWebApp\WEB-INF\lib
> This happens even when there has been no resolve and no new or updated jars exist

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.