Bug 7219 - escapeXml attribute provided with a null value doens't behave in spec compliant manner
Summary: escapeXml attribute provided with a null value doens't behave in spec complia...
Status: RESOLVED LATER
Alias: None
Product: Taglibs
Classification: Unclassified
Component: Standard Taglib (show other bugs)
Version: unspecified
Hardware: All All
: P3 major (vote)
Target Milestone: ---
Assignee: Tomcat Developers Mailing List
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2002-03-18 21:14 UTC by Ryan Lubke
Modified: 2004-11-16 19:05 UTC (History)
0 users


Attachments
Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.
Description Ryan Lubke 2002-03-18 21:14:53 UTC 
Given:

<c:out value="< > , \" &" escapeXml="${null}"/>

The output in this case is not escaped.  According to section 2.7 of the JSTL
1.0 public draft, if an attribute can accept dynamic values and has a fixed set
of acceptable values, and the value passed is null, then the default value
should be used.
Comment 1 Shawn Bayern 2002-03-30 19:39:19 UTC 
I believe that section 2.7 is being modified to apply only to String values.  
In this case, the RI coerces "null" to "false" per section A.7.4:  'escapeXml' 
is a boolean attribute.

Since I'm pretty sure that this spec modification will go through, let's mark 
this closed for now and revisit it only if it doesn't get addressed.