"Vjeran Marcinko" <[EMAIL PROTECTED]> writes:
I plan to put a patch for this into 2.3.1 (using
commons-logging.properties and no longer hard-code the log4j factory).
However, for me, Turbine based applications run fine with Tomcat
5.0.25 to 5.0.27. Never had any problems. I use the Tomcat5 from jpackage
for deployment and the binary releases from jakarta for testing.
What errors do you see? Do you have any special configuration done
to server.xml?
Regards
Henning
>Hi folks.
>Current version of Turbine 2.3 doesn't work in Tomcat5 because Tomcat's
>classloader system uses commons-logging.jar and jmx.jar before looking into
>some .war (they call it system classpath which has higher priority than war
>libs). It wouldn't be a problem if Turbine's servlet doesn't use
>Log4JFactory (from commons-logging's *implementation package*, not API)
>which is excluded in newer versions of commons-logging. Is there some
>compiled version of Turbine 2.3 with this problem fixed ?
>Regards,
>Vjeran
>---------------------------------------------------------------------
>To unsubscribe, e-mail: [EMAIL PROTECTED]
>For additional commands, e-mail: [EMAIL PROTECTED]
--
Dipl.-Inf. (Univ.) Henning P. Schmiedehausen INTERMETA GmbH
[EMAIL PROTECTED] +49 9131 50 654 0 http://www.intermeta.de/
RedHat Certified Engineer -- Jakarta Turbine Development -- hero for hire
Linux, Java, perl, Solaris -- Consulting, Training, Development
"Fighting for one's political stand is an honorable action, but re-
fusing to acknowledge that there might be weaknesses in one's
position - in order to identify them so that they can be remedied -
is a large enough problem with the Open Source movement that it
deserves to be on this list of the top five problems."
-- Michelle Levesque, "Fundamental Issues with
Open Source Software Development"
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
