DO NOT REPLY [Bug 24179] New: - Including CATALINA_BASE in the catalina and common class loaders construction

[bu...@apache.org]

DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG 
RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT
<http://nagoya.apache.org/bugzilla/show_bug.cgi?id=24179>.
ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND 
INSERTED IN THE BUG DATABASE.

http://nagoya.apache.org/bugzilla/show_bug.cgi?id=24179

Including CATALINA_BASE in the catalina and common class loaders construction

           Summary: Including CATALINA_BASE in the catalina and common class
                    loaders construction
           Product: Tomcat 4
           Version: 4.1.27
          Platform: Other
        OS/Version: Other
            Status: NEW
          Severity: Enhancement
          Priority: Other
         Component: Catalina
        AssignedTo: tomcat-dev@jakarta.apache.org
        ReportedBy: rruiz@gridsystems.com


The idea is to modify org.apache.catalina.startup.Bootstrap (or implement a 
subclass) to include the following paths in the base class loaders:

commonLoader:
  - $CATALINA_BASE/common/classes
  - $CATALINA_BASE/common/endorsed/*.jar
  - $CATALINA_BASE/common/lib/*.jar
catalinaLoader:
  - $CATALINA_BASE/server/classes
  - $CATALINA_BASE/server/lib/*.jar

A reason for this modification would be the next scenario:

Suppose a web-enabled solution that uses a Tomcat server as a servlet 
container, but that involves the development or usage of custom valves, 
listeners, socket factories and so.

Some of these applications will require some extra libraries to be added to the 
common class loader. Some others will require them to be in the catalina class 
loader.

Currently, the only way to get this to work is to customize a full Tomact 
installation, putting the additional jars in common/lib or server/lib.

This means that, in a development environment, each programmer will need a 
local full tomcat installed for the product to be tested.

If you multiply this by N developers, and by M different products, the waste of 
space begins to become important.

If those "tomcat components" are shared among products, and different versions 
are incompatible, the same can be applied to a customer production environment, 
where using a shared instance would be desirable, but it would not be possible 
due to library incompatibilities.

---------------------------------------------------------------------
To unsubscribe, e-mail: tomcat-dev-unsubscribe@jakarta.apache.org
For additional commands, e-mail: tomcat-dev-help@jakarta.apache.org