Bug 8225 - TLV incorrectly flagging error against <fmt:setBundle> if var is specified and scope is not.
Summary: TLV incorrectly flagging error against <fmt:setBundle> if var is specified an...
Status: RESOLVED FIXED
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-17 20:13 UTC by Ryan Lubke
Modified: 2004-11-16 19:05 UTC (History)
1 user (show)


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-17 20:13:07 UTC 
According to the spec, the followng:

<fmt:setBundle basename="some.Resources scope="request"/>

Will set the javax.servlet.jsp.jstl.fmt.localizationContext so the scope
specified.

Instead, the following is received:

Illegal scope attribute without var in "fmt:setBundle" tag
Comment 1 Jan Luehe 2002-04-17 21:00:34 UTC 
Fixed. <fmt:setBundle> now is allowed to have a "dangling" scope.
Comment 2 Jan Luehe 2002-04-17 21:10:11 UTC 
BTW: The bug synopsis should have been:

  TLV incorrectly flagging error against <fmt:setBundle> if scope is specified
and var is not.

I think you got it the other way around. ;-)
Comment 3 Jan Luehe 2002-04-22 19:28:23 UTC 
*** Bug 8376 has been marked as a duplicate of this bug. ***