3 Replies Latest reply on Mar 10, 2017 11:01 AM by Antoine Rey

    JSTL fmt tag fails in JBoss EAP 6.2

    Amarnath RC Newbie

      The following error is thrown in Spring mvc based web application. I think this happens since Jboss core JSTL module is being loaded along with application jars.

       

       

       

      JBWEB000236: Servlet.service() for servlet controldispatcher threw exception: java.lang.ClassCastException: org.springframework.web.servlet.support.JstlUtils$SpringLocalizationContext cannot be cast to java.lang.String

        at org.apache.taglibs.standard.tag.common.fmt.BundleSupport.getLocalizationContext(BundleSupport.java:178) [jboss-jstl-api_1.2_spec-1.0.3.Final-redhat-2.jar:1.0.3.Final-redhat-2]

        at org.apache.taglibs.standard.tag.common.fmt.SetLocaleSupport.getFormattingLocale(SetLocaleSupport.java:320) [jboss-jstl-api_1.2_spec-1.0.3.Final-redhat-2.jar:1.0.3.Final-redhat-2]

        at org.apache.taglibs.standard.tag.common.fmt.ParseDateSupport.doEndTag(ParseDateSupport.java:174) [jboss-jstl-api_1.2_spec-1.0.3.Final-redhat-2.jar:1.0.3.Final-redhat-2]

        at org.apache.jsp.display.search.proposalDetailed.searchProposalBody_jsp._jspx_meth_fmt_005fparseDate_005f0(searchProposalBody_jsp.java:1403)

       

       

      I've tried to exclude jboss jstl api in Jboss-deployment-structure xml but no luck. Can someone help with appropiate deployment xml for this or any other solution appreciated?

       

       

      P.S. I think this issue is resolved in wildFly as class loading techniques are changed. But one of my customer wants to be in EAP 6.2, so I'm stuck with this error.

       

      Regards,

      Amarnath