Bug 8384

Summary: Translation error fails to against <x:parse> if scopeDom is specified and varDom is not.
Product: Taglibs Reporter: Ryan Lubke <Ryan.Lubke>
Component: Standard TaglibAssignee: Tomcat Developers Mailing List <dev>
Status: RESOLVED WORKSFORME    
Severity: major    
Priority: P3    
Version: unspecified   
Target Milestone: ---   
Hardware: All   
OS: All   

Description Ryan Lubke 2002-04-22 23:11:17 UTC
The syntax description on page 11-154 of the PFD spec would indicate
that either var or varDom must be specified when using the action.

If using scopeDom is specified, varDom must also be specified.
Comment 1 Shawn Bayern 2002-04-23 19:52:50 UTC
Ryan - are you sure you're looking for the right kind of error?  In the current
RI, this constraint happens to be enforced by a TEI, not a TLV.  I believe the
RI is compliant in this regard.  For <x:parse scopeDom="foo"/>, I get the
following translation-time error:

org.apache.jasper.compiler.CompileException: /xml/foo.jsp(1,0) Attributes are i
nvalid according to TagInfo