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.

Hermod

-----Opprinnelig melding-----
Fra: Joe Germuska [mailto:[EMAIL PROTECTED]
Sendt: 6. oktober 2004 06:04
Til: Struts Users Mailing List
Emne: [OT] Display Tag Library problems with Weblogic 6.1


I'm trying for the first time to deploy the "displaytag" library to a 
Weblogic 6 server, and I'm getting an annoying error which I was not 
getting while developing locally under Tomcat 4.  Since I know a lot 
of Struts users use displaytag, and since I'm not subscribed to that 
list, I thought I'd see if anyone had any ideas.

When using the "displaytag-1.0-rc1.jar" retrieved from the iBiblio 
Maven repository, I get this error:

/Results.jsp(3): Error in using tag library 
uri='http://displaytag.sf.net/' prefix='display': For tag 'table', 
cannot load extra info class 'org.displaytag.tags.TableTagExtraInfo'
  probably occurred due to an error in /Results.jsp line 3:
<%@ taglib uri="http://displaytag.sf.net/"; prefix="display" %>

Changing the JSP so that it attempts to simply access the static 
'class' member of the TableTagExtraInfo class gets me an error "class 
file has wrong version 48.0, should be 47.0".  So... I decided to 
just try rebuilding the JAR from SourceForge CVS.  When I put that 
version of the JAR in place, the above error disappears, but now I 
get:

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.

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 this point, I'm sending this out in part just to get a solution 
into the google-net in case anyone else comes across the same 
problem.  But also, it just seems like a fragile little hack, and I'm 
wondering if anyone knows anything more about it.

Is anyone using displaytag with Weblogic 6.1? Thanks for any 
experiences, or even just ideas about how to debug it further.

Thanks,
   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


* * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * *

This email with attachments is solely for the use of the individual or
entity to whom it is addressed. Please also be aware that the DnB NOR Group
cannot accept any payment orders or other legally binding correspondence with
customers as a part of an email. 

This email message has been virus checked by the virus programs used
in the DnB NOR Group.

* * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * *


---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Reply via email to