Bug 8384 - Translation error fails to against <x:parse> if scopeDom is specified and varDom is not.
Summary: Translation error fails to against <x:parse> if scopeDom is specified and var...
Status: RESOLVED WORKSFORME
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-04-22 23:11 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-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