Bug 1136170

Summary:	Trigger JSP recompilation when timestamp changes in any way
Product:	[JBoss] JBoss Enterprise Application Platform 6	Reporter:	James Livingston <jlivings>
Component:	Web	Assignee:	Rémy Maucherat <rmaucher>
Status:	CLOSED WONTFIX	QA Contact:	Radim Hatlapatka <rhatlapa>
Severity:	unspecified	Docs Contact:	Russell Dickenson <rdickens>
Priority:	unspecified
Version:	6.3.0	CC:	joallen
Target Milestone:	---
Target Release:	---
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:		Doc Type:	Bug Fix
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2014-09-02 23:23:21 UTC	Type:	Bug
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	---	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:
Embargoed:

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.