Skip to Content
0
Former Member
Jul 26, 2005 at 01:42 PM

Problem with Custom Tags on WAS 6.2

10 Views

Hi

I have deployed a web application onto WAS (as an ear file) which makes use of custom tags, namely the displaytags written by Sourceforge.net (http://displaytag.sourceforge.net).

When a JSP page is invoked which uses any of these display tags, I receive the following error:

Internal Server Error 500!

com.inqmy.services.servlets_jsp.server.jsp.ParseException: ID17120: Unknown class name

at com.inqmy.services.servlets_jsp.server.jsp.TagBeginGenerator.convertString(TagBeginGenerator.java:407)

at com.inqmy.services.servlets_jsp.server.jsp.TagBeginGenerator.generateSetters(TagBeginGenerator.java:193)

at com.inqmy.services.servlets_jsp.server.jsp.TagBeginGenerator.generateServiceMethodStatements(TagBeginGenerator.java:218)

at com.inqmy.services.servlets_jsp.server.jsp.TagBeginGenerator.generate(TagBeginGenerator.java:268)

at com.inqmy.services.servlets_jsp.server.jsp.syntax.JspElement.customTagAction(JspElement.java:375)

at com.inqmy.services.servlets_jsp.server.jsp.syntax.JspElement.action(JspElement.java:134)

at com.inqmy.services.servlets_jsp.server.jsp.syntax.ElementCollection.action(ElementCollection.java:52)

at com.inqmy.services.servlets_jsp.server.jsp.JSPParser.parse(JSPParser.java:259)

at com.inqmy.services.servlets_jsp.server.jsp.JSPServlet.getClassName(JSPServlet.java:320)

at com.inqmy.services.servlets_jsp.server.jsp.JSPServlet.service(JSPServlet.java:194)

at javax.servlet.http.HttpServlet.service(HttpServlet.java:1264)

at com.inqmy.services.servlets_jsp.server.FilterChainImpl.runServlet(FilterChainImpl.java:136)

at com.inqmy.services.servlets_jsp.server.FilterChainImpl.doFilter(FilterChainImpl.java:69)

at bucksOnline.filters.StatsFilter.doFilter(StatsFilter.java:115)

at com.inqmy.services.servlets_jsp.server.FilterChainImpl.doFilter(FilterChainImpl.java:64)

at com.inqmy.services.servlets_jsp.server.RunServlet.runSerlvet(RunServlet.java:123)

at com.inqmy.services.servlets_jsp.server.ServletsAndJspImpl.startServlet(ServletsAndJspImpl.java:848)

at com.inqmy.services.httpserver.server.RequestAnalizer.checkFilename(RequestAnalizer.java:536)

at com.inqmy.services.httpserver.server.RequestAnalizer.handle(RequestAnalizer.java:223)

at com.inqmy.services.httpserver.server.Response.handle(Response.java:164)

at com.inqmy.services.httpserver.server.HttpServerFrame.request(HttpServerFrame.java:882)

at com.inqmy.core.service.context.container.session.ApplicationSessionMessageListener.process(ApplicationSessionMessageListener.java:36)

at com.inqmy.core.cluster.impl3.ParserRunner.run(ParserRunner.java:30)

at com.inqmy.core.thread.impl0.ActionObject.run(ActionObject.java:46)

at java.security.AccessController.doPrivileged(Native Method)

at com.inqmy.core.thread.impl0.SingleThread.run(SingleThread.java:132)

The taglib uri defined within the JSP is referencing the TLD directly (I know that WAS is finding the TLD, because changing the uri results in a different - more meaningful- error).

<%@ taglib uri="/WEB-INF/displaytag-12.tld" prefix="display" %>

The TLD file is correctly formatted from what I can see (it's written by sourceforge, so I trust it more than my own tags).

The classes that implement the tag functionality are located in the sourceforge provided jar file, and this is placed in the web application's lib directory.

Incidentally, the custom tags work correctly under Tomcat (standalone and embedded in JBoss).

I'd appreciate any feedback.

Thanks.