You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@tomcat.apache.org by bu...@apache.org on 2001/09/21 14:24:56 UTC

DO NOT REPLY [Bug 3763] New: - Missing CATALINA_CLASSPATH env or Context/Classpath element

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=3763>.
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=3763

Missing CATALINA_CLASSPATH env or Context/Classpath element

           Summary: Missing CATALINA_CLASSPATH env or Context/Classpath
                    element
           Product: Tomcat 4
           Version: Unknown
          Platform: PC
        OS/Version: Windows NT/2K
            Status: NEW
          Severity: Normal
          Priority: Other
         Component: Catalina
        AssignedTo: tomcat-dev@jakarta.apache.org
        ReportedBy: mmc@mortench.net


The current strategy used in CATALINA to handle classpath problems is
really annoying when using CATALINA for development in non-trivial 
situations. I have several libraries inc. a Oracle database driver
which I do not want to copy into CATALINA or to include in my webapp
(since some of them may be updated and I do not want to keep track of
different version). 

Rather I would prefer to be able to simply add a global CATALINA_CLASSPATH 
(e.x. CATALINA_CLASSPATH=%ORACLE_HOME%\jdbc\lib\classes12.zip) AND/OR a webapp 
classpath in web.xml (i.e. <Context path="/frontend" ... classpath="%
ORACLE_HOME%\jdbc\lib\classes12.zip"/>).

I guess this would involve changing the default startup script AND/OR
some DTD etc. Just changing the startup script would help a lot (I have
handcode some script changes myself but would like this to be standard)

P.S. I selected unknown under version in this report, but I mean final 4.0 
release (not on list)