[jboss-jira] [JBoss JIRA] Commented: (JBAS-4970) Hot redeployment displaying old content
Remy Maucherat (JIRA)
jira-events at lists.jboss.org
Tue Dec 4 09:44:51 EST 2007
[ http://jira.jboss.com/jira/browse/JBAS-4970?page=comments#action_12390453 ]
Remy Maucherat commented on JBAS-4970:
--------------------------------------
Is your issue limited to JSPs ? If so, the work folder may not get deleted when you replace the WAR with a new one (rather than delete, wait, put a new one), and the timestamp of the compiled JSP needs to be older than that of the newly deployed JSP source for recompilation to occur.
> Hot redeployment displaying old content
> ---------------------------------------
>
> Key: JBAS-4970
> URL: http://jira.jboss.com/jira/browse/JBAS-4970
> Project: JBoss Application Server
> Issue Type: Bug
> Security Level: Public(Everyone can see)
> Components: Web (Tomcat) service
> Affects Versions: JBossAS-5.0.0.Beta2
> Environment: Linux 2.6.22-14-generic
> java version "1.5.0_13"
> Java(TM) 2 Runtime Environment, Standard Edition (build 1.5.0_13-b05)
> Java HotSpot(TM) Server VM (build 1.5.0_13-b05, mixed mode)
> Reporter: Petr Hejl
> Assigned To: Remy Maucherat
> Priority: Critical
>
> If the war is hot redeployed (delete war, copy the new one) fast enough, the server still displays the old content. It notes the new one - the expanded content at tmp/deploy/webaap-....war is the fresh one, however the (freshly) compiled jsps (in work/jboss.web/localhost/webapp/org/apache/jsp) are still the old.
> Same occurs for the war inside the ear. Occurs for both J2EE1.4 and Java EE5 projects.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
More information about the jboss-jira
mailing list