Joe,
Dumb question for you: Is the taglib line in your displaytag using jsp really <%@ taglib uri="http://displaytag.sf.net/"; prefix="display" %>
The uri is arbitrary, and just needs to match up with one <taglib-uri> element value in the web.xml file. I chose to use the uris that will work with TLD auto-discovery for the eventuality that this app is used on a newer servlet container. I knew the TLD was being read, because the errors were based on stuff that could only happen once it was processed -- "can't open X class" where "X class" is defined in the TLD, etc.
Thinking about this part this morning:
weblogic.servlet.jsp.JspException: (line 43): for tag 'table', property 'name' of tag handler class 'org.displaytag.tags.TableTag', the value must be a runtime expression "<%=...%>", since we cannot do an automatic conversion from "sessionScope.REGISTRATIONS" to type 'java.lang.Object' and there is no custom property editor for that type
Now, this just seems ridiculous, as what conversion would need to be made to "java.lang.Object"? Also, I thought that runtime expressions could only be Strings.
I realized that most older tags probably use Strings, primitives, or primitive wrapper classes as their property types, while displaytag uses "Object" for its "list" property because it can take advantage of JSTL-EL so that one can directly assign the object intended for display. It's still weird, because the result of a runtime expression is always a String, so the net difference is zero.
Well, believe it or not, using a Scriptlet to create a String whose value is "sessionScope.REGISTRATIONS" and then inlining that using an RT-expression, the thing just worked!
<% String freakishWeblogic61Hack = "sessionScope.REGISTRATIONS"; %> <display:table name="<%= freakishWeblogic61Hack %>" export="true" id="row" requestURI="" cellpadding="5" cellspacing="0">
At 8:23 AM +0200 10/6/04, [EMAIL PROTECTED] wrote:
Hei
When you get a class version error, it often means that you are running under a version og Java that is lower than the one used to compile the class.
Yes, I partially understand this. Weblogic 6.1 is designed to run with JDK 1.3, and we've never tried to make it run under JDK 1.4, since we're moving new projects to JBoss anyway. That's why I rebuilt the JAR from the displaytag CVS repository. However, I don't completely understand this, because I didn't change the JAVA_HOME that maven used to build the jar, which means that the one I built (which works) was also built with Java 1.4. Do I have some compatibility setting enabled about which I was unaware?
Thanks for the responses, folks. And, as noted, ultimately, it is working, and if we need to use displaytag for any of our other legacy weblogic apps, it seems as though this solution will work...
Joe
--
Joe Germuska [EMAIL PROTECTED] http://blog.germuska.com "In fact, when I die, if I don't hear 'A Love Supreme,' I'll turn back; I'll know I'm in the wrong place."
- Carlos Santana
