TLD is not loaded from CLASSPATH using Tomcat 7
-----------------------------------------------

                 Key: OFBIZ-4591
                 URL: https://issues.apache.org/jira/browse/OFBIZ-4591
             Project: OFBiz
          Issue Type: Bug
          Components: framework
    Affects Versions: SVN trunk
         Environment: Ubntu
            Reporter: Chatree Srichart
            Priority: Critical


Hi community.
I have a problem when I render a JSP page which is defined a taglib, for 
example:

<%@ taglib prefix="c" uri="http://java.sun.com/jsp/jstl/core"%>

 The problem is TLD definition files are not loaded from CLASSPATH using Tomcat 
7.
To solve this problem we need to delete this line from CatalinaContainer.java 
file:

standardJarScanner.setScanClassPath(false);

because the standard jar scanner is set the default value as "true"

After we have done above, we will get these problems.

=========================================================
1. JAR files are conflicted by different webapp contexts
=========================================================

The ScheduledExecutorService that submit all webapp contexts does not run them 
respectively. For example:

Context(1)
Context(2)
Context(3)

A particular context will read all JAR files from CLASSPATH. The problem is, 
for example, the Context(2) will start to read all JAR files even though the 
Context(1) does not finish its task yet. So the Context (2) will not be able to 
read some JAR file that the Context(1) is reading and causes an error.

===========================================================
2. WebslingerAccessLogValve class does not support Tomcat 7
===========================================================

If the jar scanner scan jar files from CLASSPATH, it will find 
WebslingerAccessLogValve class which does not support Tomcat 7

=======================================================
3. groovy.jmx.builder.package-info class cannot be loaded
=======================================================

groovy.jmx.builder.package-info class cannot be loaded because its name is 
incorrect. If I remove this class from 
framework/base/lib/scripting/groovy-all-1.7.7.jar file, this line in macros.xml 
will cause an error:

<taskdef name="groovyc" classname="org.codehaus.groovy.ant.Groovyc" 
classpathref="groovy.class.path"/>

============================
4. Starting time will slower
============================

A particular webapp context will spend more time to parse JAR file from 
CLASSPATH to find TLD definition files.



However I can avoid the TLD problem by copying JAR files that contain TLD 
definition files into /WEB-INF/lib directory of a particular webapp

Lastly, I am not sure if we need this feature in the trunk but I think it is 
useful. If so, please help me to solve the problems.

Regards,
Chatree Srichart

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: 
https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira

        

Reply via email to