2 Replies Latest reply on Feb 27, 2012 11:41 PM by saurabh agrawal

    disable TLD verification

    saurabh agrawal Newbie

      hi,

       

      please inform me where to disable tld verification in jboss6.

       

      thanks

        • 1. Re: disable TLD verification
          saurabh agrawal Newbie

          please reply some one.......

          • 2. Re: disable TLD verification
            saurabh agrawal Newbie

            To elaborate the case…providing an example of the issue which we are facing while migrating application from Weblogic to JBOSS:

             

            Error is appearing due to either TLD tag’s attribute, used on jsp page, is not defined in TLD file or the attribute is defined but on JSP page attribute is being used in different case(lower/upper/Camel case).

             

            Example :

            Error at run time :

             

            ERROR [org.apache.catalina.core.ContainerBase.[jboss.web].[localhost].[/].[jsp]] Servlet.service() for servlet jsp threw exception: org.apache.jasper.JasperException: /scripts/abc.jsp(86,5) Attribute id invalid for tag text according to TLD

             

            The code of abc.jsp :

             

            <html:text name="xyz" property="FromDate" id="FromDate"/>

             

            The code of corresponding TLD file :

             

            <tag>

            <name>text</name>

            <tagclass>org.apache.struts.taglib.html.TextTag</tagclass>

            <attribute>

            <name>name</name>

            <required>false</required>

            <rtexprvalue>true</rtexprvalue>

            </attribute>

            <attribute>

            <name>property</name>

            <required>true</required>

            <rtexprvalue>true</rtexprvalue>

            </attribute>

            .

            .

            .

            </tag>

             

            In this TLD file, id attribute is not defined for text tag. If I define the attribute in the TLD file then it will start working fine.

             

            Please note that we are running the same code on Weblogic without any issue.