1 Reply Latest reply on Feb 14, 2011 6:46 PM by henk de boer

    .tld from jar in default/lib not read?

    henk de boer Master

      In an EAR application normally deployed to JBoss AS 5.1 I have an oscache jar in /server/default/lib. It was necessary to put it there, since the application is using class loader isolation (loader repository in jboss-app.xml) and os cache is used as cache for Hibernate. When it shipped in the EAR, Hibernate couldn't find it.

       

      The oscache .jar also contains a .tld that's used by the web module in the EAR.

       

      When I move this application to JBoss AS 6, I got the following exception when loading a page that references the namespace from the os cache .jar:

       

      org.apache.jasper.JasperException: The absolute uri: http://www.opensymphony.com/oscache cannot be resolved in either web.xml or the jar files deployed with this application
       org.apache.jasper.compiler.DefaultErrorHandler.jspError(DefaultErrorHandler.java:51)
       org.apache.jasper.compiler.ErrorDispatcher.dispatch(ErrorDispatcher.java:409)
       org.apache.jasper.compiler.ErrorDispatcher.jspError(ErrorDispatcher.java:116)
       org.apache.jasper.compiler.TagLibraryInfoImpl.generateTLDLocation(TagLibraryInfoImpl.java:239)
       org.apache.jasper.compiler.TagLibraryInfoImpl.<init>(TagLibraryInfoImpl.java:152)
       org.apache.jasper.compiler.Parser.parseTaglibDirective(Parser.java:386)
       org.apache.jasper.compiler.Parser.parseDirective(Parser.java:448)
       org.apache.jasper.compiler.Parser.parseElements(Parser.java:1398)
       org.apache.jasper.compiler.Parser.parse(Parser.java:130)
       org.apache.jasper.compiler.ParserController.doParse(ParserController.java:255)
       org.apache.jasper.compiler.ParserController.parse(ParserController.java:103)
       org.apache.jasper.compiler.Compiler.generateJava(Compiler.java:196)
       org.apache.jasper.compiler.Compiler.compile(Compiler.java:358)
       org.apache.jasper.compiler.Compiler.compile(Compiler.java:338)
       org.apache.jasper.compiler.Compiler.compile(Compiler.java:325)
       org.apache.jasper.JspCompilationContext.compile(JspCompilationContext.java:607)
       org.apache.jasper.servlet.JspServletWrapper.service(JspServletWrapper.java:312)
       org.apache.jasper.servlet.JspServlet.serviceJspFile(JspServlet.java:326)
       org.apache.jasper.servlet.JspServlet.service(JspServlet.java:253)
       javax.servlet.http.HttpServlet.service(HttpServlet.java:847)
      
      

       

      Is there any way I can resolve this? For the time being I would like the app to be compatible with both JBoss AS 5.1 and JBoss AS 6.

        • 1. .tld from jar in default/lib not read?
          henk de boer Master

          Never mind this question. There were a couple of other errors relating to differences between JBoss AS 5 and JBoss AS 6.

           

          For some reason however those errors where not shown in the log while starting, and the web module was started even though it actually shouldn't have. I did a couple of things and then after a restart those errors were shown and the web module (rightfully) wasn't started.

           

          It's a bit hard to trace back what exactly happened, so just forget about this one. It maybe was collateral damage.