Bug 1136170 - Trigger JSP recompilation when timestamp changes in any way
Summary: Trigger JSP recompilation when timestamp changes in any way
Keywords:
Status: CLOSED WONTFIX
Alias: None
Product: JBoss Enterprise Application Platform 6
Classification: JBoss
Component: Web
Version: 6.3.0
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
: ---
Assignee: Rémy Maucherat
QA Contact: Radim Hatlapatka
Russell Dickenson
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2014-09-02 05:41 UTC by James Livingston
Modified: 2018-12-09 18:28 UTC (History)
1 user (show)

Fixed In Version:
Clone Of:
Environment:
Last Closed: 2014-09-02 23:23:21 UTC
Type: Bug
Embargoed:

Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Apache Bugzilla 33453 0 None None None Never
Red Hat Issue Tracker JBPAPP-8362 0 Major Reopened .jsp fails to recompile after context redeployment 2014-09-08 14:21:35 UTC

Description James Livingston 2014-09-02 05:41:27 UTC 
Jasper triggers recompilation of JSPs if the timestamp on the .jsp file is newer than the .class file. This can lead to not recompiling when the JSP changes, if the timestamp of the new JSP is newer than the old JSP but not newer than the compiled version.

The upstream bug is https://issues.apache.org/bugzilla/show_bug.cgi?id=33453. The change was made for Tomcat 7, but it may be possible to backport to JBossWeb 7
Comment 1 Rémy Maucherat 2014-09-02 07:31:32 UTC 
Asked for and refused a while ago: https://issues.jboss.org/browse/JBPAPP-8362
The fix adds complexity and I still don't see the point.
Comment 2 James Livingston 2014-09-02 23:23:21 UTC 
Thanks for the link, I was looking in JBPAPP6/WFLY/JBWEB and not JBPAPP. I'm happy to mark this WONTFIX then.
Note You need to log in before you can comment on or make changes to this bug.