0 Replies Latest reply on Dec 29, 2004 2:57 AM by Frank Cornelis

    JBoss 4 and JSTL 1.1

    Frank Cornelis Apprentice

      In a previous posting 'Standard taglib with jboss 3.2.3, tomcat 5' someone suggested to set, in the Tomcat 5 SAR, in jboss-service.xml, UseJBossWebLoader to false. Now JBoss 4.0.0 comes with a default false for this attribute. But shouldn't it be set to true when you want to install JSTL within the JBoss server lib directory (within my WEB-INF/lib seems dirty to me since JSTL will probably be included in J2EE in the future). From what I can make up out of it you have to put it to true in order for Tomcat to use the JBoss classloader and thus to find the JSTL tag libs. If you don't set this attribute to true you get the very annoying:

      org.apache.jasper.JasperException: The absolute uri: http://java.sun.com/jsp/jstl/fmt cannot be resolved in either web.xml or the jar files deployed with this application

      The problem is that it doesn't work this way. Thus my question: how do I install JSTL in the JBoss server lib directory and let the Tomcat service locate this JSTL stuff?

      BTW: It would also make things cleaner if JBoss had a server lib/ext and in jboss-service.xml an extra
      lt classpath codebase="lib/ext" archives="*"/ gt