Bug 5673 - Change the type of property "value" in define tag from java.lang.String to java.lang.Object
Summary: Change the type of property "value" in define tag from java.lang.String to ja...
Alias: None
Product: Taglibs
Classification: Unclassified
Component: Application Taglib (show other bugs)
Version: 1.0
Hardware: All All
: P3 normal (vote)
Target Milestone: ---
Assignee: Tomcat Developers Mailing List
Depends on:
Reported: 2002-01-03 07:47 UTC by charlie
Modified: 2005-03-20 17:06 UTC (History)
0 users


Note You need to log in before you can comment on or make changes to this bug.
Description charlie 2002-01-03 07:47:49 UTC
in "define" tag, we can specify the "type" property, but the type of "value" 
property is String, so in fact the only type you can specify is 
java.lang.String. so I think maybe we should change the type of the "value" 
property to java.lang.Object. In our project, I change like this and run  my 
jsp page successfully. Here is my exam in JSP page:
<bean:define id="enum1" type="java.util.Enumeration" value="<%=data.keys()%>" />
Note: data is type of java.util.Hashtable.
If we don't change the define tag, then the jsp compiler will complain that it 
cannot cast java.util.Enumeration to java.lang.String.
Comment 1 Glenn Nielsen 2002-04-02 13:48:47 UTC
Sorry it took so long to look into your report.

It is not clear to me that you are reporting a bug in a Jakarta-Taglibs
tag library.  You mention your own tag library bug I don't see anything
which refers to a bug in a Jakarta-Taglib.
Comment 2 Glenn Nielsen 2002-04-04 18:20:51 UTC
Now I see what you mean.  You would like attribute values of any type to
be saved, not just a String.  None of the common taglibs like application,
request, session, etc. do this now, they all use String attributes.  This
was a design decision at the time to keep this taglibs simple.  And now that
the JSTL is in beta, it really supercedes these older taglibs.  This won't
be changed or fixed.