Uploaded image for project: 'Application Server 3  4  5 and 6'
  1. Application Server 3 4 5 and 6
  2. JBAS-4483

Validation error messages from TagLibraryValidator

XMLWordPrintable

    • Icon: Bug Bug
    • Resolution: Obsolete
    • Icon: Major Major
    • No Release
    • JBossAS-4.0.5.GA
    • None
    • None
    • WIndows as well as Linux

      The JSP which runs on JBoss 4.0.4 does not run on JBoss 4.0.5.

      I got the following error :

      2007-06-08 06:37:02,278 ERROR [org.apache.catalina.core.ContainerBase.[jboss.web].[localhost].[/infinity-beta].[action]] Servlet.service() for servlet action threw exception
      javax.servlet.jsp.JspException: ServletException in '/solutionreg/sla/serviceLevelAdd.jsp': <h3>Validation error messages from TagLibraryValidator for c in /solutionreg/sla/serviceLevelAdd.jsp</h3><p>null: org.xml.sax.SAXParseException: An invalid XML character (Unicode: 0x1b) was found in the CDATA section.</p><h3>Validation error messages from TagLibraryValidator for fmt in /solutionreg/sla/serviceLevelAdd.jsp</h3><p>null: org.xml.sax.SAXParseException: An invalid XML character (Unicode: 0x1b) was found in the CDATA section.</p>
      at org.apache.struts.taglib.tiles.InsertTag$InsertHandler.doEndTag(InsertTag.java:923)
      at org.apache.struts.taglib.tiles.InsertTag.doEndTag(InsertTag.java:462)
      at org.apache.jsp.csa.layout.mainLayout_jsp._jspx_meth_tiles_get_6(mainLayout_jsp.java:1564)
      at org.apache.jsp.csa.layout.mainLayout_jsp._jspx_meth_c_otherwise_2(mainLayout_jsp.java:1537)
      at org.apache.jsp.csa.layout.mainLayout_jsp._jspx_meth_c_choose_2(mainLayout_jsp.java:1373)
      at org.apache.jsp.csa.layout.mainLayout_jsp._jspService(mainLayout_jsp.java:252)
      at org.apache.jasper.runtime.HttpJspBase.service(HttpJspBase.java:97)
      at javax.servlet.http.HttpServlet.service(HttpServlet.java:810)
      at org.apache.jasper.servlet.JspServletWrapper.service(JspServletWrapper.java:334)
      at org.apache.jasper.servlet.JspServlet.serviceJspFile(JspServlet.java:314)
      at org.apache.jasper.servlet.JspServlet.service(JspServlet.java:264)
      at javax.servlet.http.HttpServlet.service(HttpServlet.java:810)
      at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:252)
      at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:173)
      at org.apache.catalina.core.ApplicationDispatcher.invoke(ApplicationDispatcher.java:672)

      Snippet of the java code created for the JSP by JBoss :

      private boolean _jspx_meth_tiles_get_6(javax.servlet.jsp.tagext.JspTag _jspx_th_c_otherwise_2, PageContext _jspx_page_context)
      throws Throwable {
      PageContext pageContext = _jspx_page_context;
      JspWriter out = _jspx_page_context.getOut();
      // tiles:get
      org.apache.struts.taglib.tiles.GetTag _jspx_th_tiles_get_6 = (org.apache.struts.taglib.tiles.GetTag) _jspx_tagPool_tiles_get_name_nobody.get(org.apache.struts.taglib.tiles.GetTag.class);
      _jspx_th_tiles_get_6.setPageContext(_jspx_page_context);
      _jspx_th_tiles_get_6.setParent((javax.servlet.jsp.tagext.Tag) _jspx_th_c_otherwise_2);
      _jspx_th_tiles_get_6.setName("content");
      int _jspx_eval_tiles_get_6 = _jspx_th_tiles_get_6.doStartTag();
      if (_jspx_th_tiles_get_6.doEndTag() == javax.servlet.jsp.tagext.Tag.SKIP_PAGE) {---------------LINE 1564
      _jspx_tagPool_tiles_get_name_nobody.reuse(_jspx_th_tiles_get_6);
      return true;
      }
      _jspx_tagPool_tiles_get_name_nobody.reuse(_jspx_th_tiles_get_6);
      return false;
      }

      See the Line 1564, which is giving the problem.

      As mentioned earlier, the same code works on JBoss' earlier version i.e. JBoss 4.0.4

      Has JBoss become more stringent in interpreting the TLDs which is causing this problem?
      This issue is critical for us as we are planning to use JBoss 4.0.5 GA in production.

              Unassigned Unassigned
              prashant78_jira Prashant Kothawade (Inactive)
              Votes:
              0 Vote for this issue
              Watchers:
              0 Start watching this issue

                Created:
                Updated:
                Resolved: