0005200: when there is web-fragment.xml, jsp with jstl is not compiled correctly

Viewing Issue Simple Details [ Jump to Notes ]

[ View Advanced ] [ Issue History ] [ Print ]

Category

Severity

Reproducibility

Date Submitted

Last Update

0005200

[Resin]

major

always

08-30-12 10:02

08-30-12 13:46

Reporter

evernat

View Status

public

Assigned To

ferg

Priority

normal

Resolution

fixed

Status

closed

Product Version

4.0.29

Summary

0005200: when there is web-fragment.xml, jsp with jstl is not compiled correctly

Description

The issue started here:
https://code.google.com/p/javamelody/issues/detail?id=244 [^]

A webapp is deployed in Resin 4.0.29.
This webapp contains in WEB-INF/lib, a jar file. And this jar file contains a META-INF/web-fragment.xml.
This webapp also contains "index.jsp", with jstl: "${1+10}".
But when displayed, index.jsp returns "${1+10}" as is (not good).
After removing the web-fragment.xml from the jar file, index.jsp returns "11" (good).

It is expected that "11" is displayed by index.jsp when there is web-fragment.xml.
Why a standard web-fragment.xml would prevent index.jsp to compile correctly?

To reproduce the issue, deploy in Resin 4.0.29 the attached test-ko.war and display index.jsp in a browser: "${1+10}" (not good).
Then deploy the attached test.war (which is the same without web-fragment.xml) and display index.jsp: "11".

Additional Information

Attached Files

test-ko.war [^] (1,723,281 bytes) 08-30-12 10:02

test.war [^] (1,722,495 bytes) 08-30-12 10:20

Relationships

Notes
(0006028) ferg 08-30-12 13:46	jsp/013f

Issue History
Date Modified	Username	Field	Change
08-30-12 10:02	evernat	New Issue
08-30-12 10:02	evernat	File Added: test-ko.war
08-30-12 10:20	evernat	File Added: test.war
08-30-12 10:21	evernat	Issue Monitored: evernat
08-30-12 13:46	ferg	Note Added: 0006028
08-30-12 13:46	ferg	Assigned To	=> ferg
08-30-12 13:46	ferg	Status	new => closed
08-30-12 13:46	ferg	Resolution	open => fixed
08-30-12 13:46	ferg	Fixed in Version	=> 4.0.31

Mantis 1.0.0rc3[^]

32 total queries executed.
26 unique queries executed.