Jetty
  1. Jetty
  2. JETTY-134

JSP 2.1 taglibs are incompatible with WebAppContext.setExtract(false)

    Details

    • Type: Bug Bug
    • Status: Resolved Resolved
    • Priority: Minor Minor
    • Resolution: Fixed
    • Affects Version/s: 6.1.16
    • Fix Version/s: 7.5.1
    • Component/s: JSP
    • Labels:
      None
    • Environment:
      Windows XP, J2SE 1.5.0_08
    • Number of attachments :
      1

      Description

      When packaged into a WAR, web site that otherwise works well (on 5 & 6) fails to work at all.

      org.apache.jasper.JasperException: PWC6180: Unable to initialize TldLocationsCache
      at org.apache.jasper.compiler.TldLocationsCache.init(TldLocationsCache.java:347)
      at org.apache.jasper.compiler.TldLocationsCache.getLocation(TldLocationsCache.java:293)
      at org.apache.jasper.JspCompilationContext.getTldLocation(JspCompilationContext.java:582)
      at org.apache.jasper.compiler.Parser.parseTaglibDirective(Parser.java:469)
      at org.apache.jasper.compiler.Parser.parseDirective(Parser.java:546)
      at org.apache.jasper.compiler.Parser.parseElements(Parser.java:1612)
      at org.apache.jasper.compiler.Parser.parse(Parser.java:154)
      at org.apache.jasper.compiler.ParserController.doParse(ParserController.java:210)
      at org.apache.jasper.compiler.ParserController.parse(ParserController.java:111)
      at org.apache.jasper.compiler.Compiler.generateJava(Compiler.java:267)
      at org.apache.jasper.compiler.Compiler.compile(Compiler.java:620)
      at org.apache.jasper.compiler.Compiler.compile(Compiler.java:602)
      at org.apache.jasper.JspCompilationContext.compile(JspCompilationContext.java:618)
      at org.apache.jasper.servlet.JspServletWrapper.service(JspServletWrapper.java:329)
      at org.apache.jasper.servlet.JspServlet.serviceJspFile(JspServlet.java:440)
      at org.apache.jasper.servlet.JspServlet.service(JspServlet.java:335)
      at redcondor.web.servlets.jsp.JasperServlet$Compiler.compile(JasperServlet.java:115)
      at redcondor.web.servlets.jsp.JasperServlet$Compiler.run(JasperServlet.java:152)

        Activity

        Hide
        Jan Bartel added a comment -

        Moved to jsp.dev.net at KinMan Chung's request: https://jsp.dev.java.net/issues/show_bug.cgi?id=1

        Show
        Jan Bartel added a comment - Moved to jsp.dev.net at KinMan Chung's request: https://jsp.dev.java.net/issues/show_bug.cgi?id=1
        Hide
        Paul Smith added a comment -

        I've hit this recently moving over from an Eclipse+Ant+Tomcat integration to Eclipse-Maven-Jetty.

        Looking at the glassfish.dev.java.net issue linked it is marked as WONTFIX which is a bit disturbing.. Any ideas here? I'm using the maven-jetty-plugin 6.1.12.rc3.

        Show
        Paul Smith added a comment - I've hit this recently moving over from an Eclipse+Ant+Tomcat integration to Eclipse-Maven-Jetty. Looking at the glassfish.dev.java.net issue linked it is marked as WONTFIX which is a bit disturbing.. Any ideas here? I'm using the maven-jetty-plugin 6.1.12.rc3.
        Hide
        Jan Bartel added a comment -

        My only suggestion is that you request the issue to be reopened at Glassfish. The JSP developers need to see that there is need to support this before they'll prioritize it.
        cheers
        Jan

        Show
        Jan Bartel added a comment - My only suggestion is that you request the issue to be reopened at Glassfish. The JSP developers need to see that there is need to support this before they'll prioritize it. cheers Jan
        Hide
        Jesse McConnell added a comment -

        moving out to next release again...have contacted the glassfish jsp folks again and hoping we can get something worked out eventually

        Show
        Jesse McConnell added a comment - moving out to next release again...have contacted the glassfish jsp folks again and hoping we can get something worked out eventually
        Hide
        Jan Bartel added a comment -

        Given the venerable age that this issue has acquired, I hesitate to declare this one actually resolved, but I tried deploying the packed test.war onto jetty-7.5.1 (which has updated the version of jsp) and with extractWAR(false) and copyWebInf(false), I could access all of the jsps that use tags.

        So, I'm closing this issue, as something seems to have changed that means that at least in some circumstances, jsps using taglibs can be used from a packed war.

        If someone retests and can find definitive proof of a problem, please reopen and attach a war file that demonstrates the problem. Even more interesting if you can point at a version of Tomcat on which deploying the packed war (not extracted) does work (as we are always evaluating whether it would be better to switch to Apache's jsp impl).

        cheers
        Jan

        Show
        Jan Bartel added a comment - Given the venerable age that this issue has acquired, I hesitate to declare this one actually resolved, but I tried deploying the packed test.war onto jetty-7.5.1 (which has updated the version of jsp) and with extractWAR(false) and copyWebInf(false), I could access all of the jsps that use tags. So, I'm closing this issue, as something seems to have changed that means that at least in some circumstances, jsps using taglibs can be used from a packed war. If someone retests and can find definitive proof of a problem, please reopen and attach a war file that demonstrates the problem. Even more interesting if you can point at a version of Tomcat on which deploying the packed war (not extracted) does work (as we are always evaluating whether it would be better to switch to Apache's jsp impl). cheers Jan

          People

          • Assignee:
            Jan Bartel
            Reporter:
            Jeffrey Aguilera
          • Votes:
            2 Vote for this issue
            Watchers:
            4 Start watching this issue

            Dates

            • Created:
              Updated:
              Resolved: