Custom Tag Capitalization Problem..

Question

All,
          OS: Windows 2000
          App Server: Weblogic 6.0 sp 2
          JDK: 1.3 (and tried 1.3.1)
          I have a set of custom tags that run fine when I use them on an app server (such as Enhydra) with JDK 1.2.2, but when I switch to JDK 1.3.x, which weblogic 6.x requires, they suddenly start generating errors with attributes which have capitalized letters in them. For example, in my taglib I have:
          <attribute>
          <name>closeConnection</name>
          <required>false</required>
          <rtexprvalue>true</rtexprvalue>
          </attribute>
          and in the support class I have:
          * Get the value of closeConnection.
          * @return value of closeConnection.
          public boolean getCloseConnection() {
          return closeConnection;
          * Set the value of closeConnection.
          * @param v Value to assign to closeConnection.
          public void setCloseConnection(String v) {
          if(v.toUpperCase().equals("TRUE")){
          this.closeConnection = true;
          } else {
          this.closeConnection = false;
          When I go to the page that this tag is on, I get the following output:
          Parsing of JSP File '/index.jsp' failed:
          /index.jsp(1): Error in using tag library uri='/cwerks' prefix='cwerks': There is no setter method for property 'closeconnection', for Tag class 'net.cwerks.taglib.MyTag'
          probably occurred due to an error in /index.jsp line 1:
          <%@ taglib uri="/cwerks" prefix="cwerks" %>
          Thu Aug 02 19:06:52 PDT 2001
          Note that the 'closeconnection' is all lowercase despite the fact that it is upper case in the tld and in the class itself.
          I came across a similar problem in weblogic 5.1 when I upgraded from JDK 1.2.2 to JDK 1.3. I tried changing the JDK for weblogic 6.0 sp 2 to 1.2.2, but a dll was missing. I also tried switching it to 1.3.1, but that did not help. It seems like introspection may have changed slightly between the two version. I'm shocked, and a bit suspicious, that I haven't seen this problem all over the newsgroups. Anyone else seen this?
          Thank you,
          Carson Gross
          [email protected]
          [att1.html]
          

Answer 1

A solution presents itself:
          The problem was NOT with capitalization. Instead, the problem was as
          follows:
          My method was for setting a boolean, but I took a string so that people
          wouldn't have to type:
          <mytags:tag foo="<%=true%>" />
          instead, they could type:
          <mytags:tag foo="true" />
          which would call the setter method with a string "true", which would be then
          converted to a boolean within my class.
          So my setter has this signature:
          public void setFoo(String s)
          and my getter has this signature:
          public boolean getFoo() /* I know this isn't standard, but isFoo doesn't
          sound good to me*/
          I can't tell if it's because JavaBeans changed slightly between jdk 1.2.2
          and 1.3.x, or if Weblogic changed the way that they do things (I suspect the
          latter, since I had things working fine in WL 5.2 w/ jdk 1.2.2 and then
          things broke with WL 5.2 w/ jdk 1.3), but this no longer returns foo as a
          valid property to be set, and since weblogic 6.x relies on JavaBeans,
          instead of straight up introspection, it barfs. (I found this out by using
          jad/emacs, a wicked combination for those who want to poke around in jars).
          Anyway, I hope I can save someone else who has this same, albeit
          specialized, problem a lot of pain by my discovery. Your getters and
          setters better be of the same type with custom tags, or weblogic w/ jdk1.3.x
          is gonna barf when parsing the tld.
          Cheers, and thank God that's behind me,
          Carson Gross
          [email protected]
          ====================================================
          "Carson Gross" <[email protected]> wrote in message
          news:[email protected]...
          The plot grows thicker...
          The tags work fine on Tomcat 3.2.2
          I deploy the example tags that came with wl60 that have more than one
          capital letter in thier attributes, and they work fine. But my tag library
          stubbornly insists on not working so long as I keep the attributes with more
          than one capital letter in. If I remove the offending attributes, or change
          them to have only one capital letter, they work, but this is not an
          acceptable solution. (I guess.)
          I even created an simple introspection class to make sure that the acutal
          methods were there. They were.
          I am at a complete loss here... I guess it's tomcat for now.
          Cheers,
          Carson Gross
          [email protected]
          "Carson Gross" <[email protected]> wrote in message
          news:[email protected]...
          All,
          OS: Windows 2000
          App Server: Weblogic 6.0 sp 2
          JDK: 1.3 (and tried 1.3.1)
          I have a set of custom tags that run fine when I use them on an app server
          (such as Enhydra) with JDK 1.2.2, but when I switch to JDK 1.3.x, which
          weblogic 6.x requires, they suddenly start generating errors with attributes
          which have capitalized letters in them. For example, in my taglib I have:
          <attribute>
          <name>closeConnection</name>
          <required>false</required>
          <rtexprvalue>true</rtexprvalue>
          </attribute>
          and in the support class I have:
          * Get the value of closeConnection.
          * @return value of closeConnection.
          public boolean getCloseConnection() {
          return closeConnection;
          * Set the value of closeConnection.
          * @param v Value to assign to closeConnection.
          public void setCloseConnection(String v) {
          if(v.toUpperCase().equals("TRUE")){
          this.closeConnection = true;
          } else {
          this.closeConnection = false;
          When I go to the page that this tag is on, I get the following output:
          Parsing of JSP File '/index.jsp' failed:
          /index.jsp(1): Error in using tag library uri='/cwerks' prefix='cwerks':
          There is no setter method for property 'closeconnection', for Tag class
          'net.cwerks.taglib.MyTag'
          probably occurred due to an error in /index.jsp line 1:
          <%@ taglib uri="/cwerks" prefix="cwerks" %>
          Thu Aug 02 19:06:52 PDT 2001
          Note that the 'closeconnection' is all lowercase despite the fact that it is
          upper case in the tld and in the class itself.
          I came across a similar problem in weblogic 5.1 when I upgraded from JDK
          1.2.2 to JDK 1.3. I tried changing the JDK for weblogic 6.0 sp 2 to 1.2.2,
          but a dll was missing. I also tried switching it to 1.3.1, but that did not
          help. It seems like introspection may have changed slightly between the two
          version. I'm shocked, and a bit suspicious, that I haven't seen this
          problem all over the newsgroups. Anyone else seen this?
          Thank you,
          Carson Gross
          [email protected]