Re: [ANNOUNCE] Tomcat 4.0 Milestone 4
Hi Craig, Thanks for the announcement email. Great work! :-) How are the Apache Connectors for Tomcat 4.0 coming along ? Is there some kind of source already available via CVS somewhere ? Cheers, Marcus On Wed, 1 Nov 2000, Craig R. McClanahan wrote: We're pleased to announce the availabililty of milestone 4 of the Tomcat 4.0 servlet container and JSP engine. Compared to milestone 3, this release reflects the following changes: * Implementation of all the changes between "public draft" and "proposed final draft" of the Servlet 2.3 and JSP 1.2 specifications. * Implementation of all remaining 2.3 / 1.2 features -- Tomcat 4.0 is now a feature complete implementation of the new specs! * Many bug fixes (see RELEASE-NOTES-4.0-M4.txt in the top level directory). Binary distributions of the new release are available from: http://jakarta.apache.org/builds/jakarta-tomcat-4.0/release/v4.0-m4 and source releases can be downloaded from: http://jakarta.apache.org/builds/jakarta-tomcat-4.0/release/v4.0-m4/src If you are planning on building Tomcat 4.0-m4 from source, you will want to pick up the corresponding distribution of the servlet API classes, found in the same directory. Users of the binary distribution need not do this -- a servlet.jar file containing the most current version of the servlet API classes is included in the "bin" directory of the binary release. Come and get it! Craig McClanahan -- . ,,$, Marcus Crafter ;$' ':Computer Systems Engineer $: : Open Software Associates GmbH $ o_)$$$: 82-84 Mainzer Landstrasse ;$,_/\ :' 60327 Frankfurt Germany ' /( \_' Email : [EMAIL PROTECTED] .Business Hours : +49 69 9757 200 : After Hours: +49 69 49086750
RE: [ANNOUNCE] Tomcat 4.0 Milestone 4
Does M4 have the connector to work with Apache or does it still only work in standalone mode? Thanks. Steve Buroff -Original Message- From: Craig R. McClanahan [mailto:[EMAIL PROTECTED]] Sent: Wednesday, November 01, 2000 11:37 PM To: [EMAIL PROTECTED]; [EMAIL PROTECTED]; [EMAIL PROTECTED]; [EMAIL PROTECTED] Subject: [ANNOUNCE] Tomcat 4.0 Milestone 4 We're pleased to announce the availabililty of milestone 4 of the Tomcat 4.0 servlet container and JSP engine. Compared to milestone 3, this release reflects the following changes: * Implementation of all the changes between "public draft" and "proposed final draft" of the Servlet 2.3 and JSP 1.2 specifications. * Implementation of all remaining 2.3 / 1.2 features -- Tomcat 4.0 is now a feature complete implementation of the new specs! * Many bug fixes (see RELEASE-NOTES-4.0-M4.txt in the top level directory). Binary distributions of the new release are available from: http://jakarta.apache.org/builds/jakarta-tomcat-4.0/release/v4.0-m4 and source releases can be downloaded from: http://jakarta.apache.org/builds/jakarta-tomcat-4.0/release/v4.0-m4/sr c If you are planning on building Tomcat 4.0-m4 from source, you will want to pick up the corresponding distribution of the servlet API classes, found in the same directory. Users of the binary distribution need not do this -- a servlet.jar file containing the most current version of the servlet API classes is included in the "bin" directory of the binary release. Come and get it! Craig McClanahan
Re: [ANNOUNCE] Tomcat 4.0 Milestone 4
"Craig R. McClanahan" wrote: We're pleased to announce the availabililty of milestone 4 of the Tomcat 4.0 servlet container and JSP engine. Compared to milestone 3, this release reflects the following changes: [...] Is this release only working in standalone mode? --mike
Re: [ANNOUNCE] Tomcat 4.0 Milestone 4
mike niemaz wrote: "Craig R. McClanahan" wrote: We're pleased to announce the availabililty of milestone 4 of the Tomcat 4.0 servlet container and JSP engine. Compared to milestone 3, this release reflects the following changes: [...] Is this release only working in standalone mode? As the release notes point out, there are still no web connectors so the answer is "yes". Web connectors are being actively worked on ... they just don't work well enough yet to start testing (you can ask Pier, who wrote the original mod_jserv code and is working on this, how much he liked having to write C code again after years of Java's freedom from pointer-related problems :-). --mike Craig
Re: [ANNOUNCE] Tomcat 4.0 Milestone 4 - cocoon security problem?
"Craig R. McClanahan" wrote: We're pleased to announce the availabililty of milestone 4 of the Tomcat 4.0 servlet container and JSP engine. Compared to milestone 3, this release reflects the following changes: Come and get it! Got it! Ooops! I lost cocoon! 2872427 Oct 31 09:38 ../archive/jakarta-tomcat-4.0-20001031.tar.gz runs cocoon, 2870683 Nov 2 08:32 ../archive/jakarta-tomcat-4.0-m4.tar.gz does not. -- My installation procedure was to unzip (gzip) 4.0-m4, rename the directory to jakarta-tomcat, 'cp -r' [old]/webapps/cocoon to jakarta-tomcat/webapps cd to jakarta-tomcat and type bin/startup.sh. JSP and servlets otherwise look fine. -- Cocoon 1.8.1-dev Publishing Engine could not be initialized. java.lang.SecurityException: sealing violation at java.net.URLClassLoader.defineClass(URLClassLoader.java:234) at java.net.URLClassLoader.access$100(URLClassLoader.java:56) at java.net.URLClassLoader$1.run(URLClassLoader.java:195) at java.security.AccessController.doPrivileged(Native Method) at java.net.URLClassLoader.findClass(URLClassLoader.java:188) at org.apache.catalina.loader.StandardClassLoader.findClass(StandardClassLoader.java:648) at org.apache.catalina.loader.StandardClassLoader.loadClass(StandardClassLoader.java:987) at org.apache.catalina.loader.StandardClassLoader.loadClass(StandardClassLoader.java:906) at java.lang.ClassLoader.loadClassInternal(ClassLoader.java:313) at java.lang.ClassLoader.defineClass0(Native Method) at java.lang.ClassLoader.defineClass(ClassLoader.java:486) at java.security.SecureClassLoader.defineClass(SecureClassLoader.java:111) at java.net.URLClassLoader.defineClass(URLClassLoader.java:248) at java.net.URLClassLoader.access$100(URLClassLoader.java:56) at java.net.URLClassLoader$1.run(URLClassLoader.java:195) at java.security.AccessController.doPrivileged(Native Method) at java.net.URLClassLoader.findClass(URLClassLoader.java:188) at org.apache.catalina.loader.StandardClassLoader.findClass(StandardClassLoader.java:648) at org.apache.catalina.loader.StandardClassLoader.loadClass(StandardClassLoader.java:987) at org.apache.catalina.loader.StandardClassLoader.loadClass(StandardClassLoader.java:906) at java.lang.ClassLoader.loadClassInternal(ClassLoader.java:313) at java.lang.ClassLoader.defineClass0(Native Method) at java.lang.ClassLoader.defineClass(ClassLoader.java:486) at java.security.SecureClassLoader.defineClass(SecureClassLoader.java:111) at java.net.URLClassLoader.defineClass(URLClassLoader.java:248) at java.net.URLClassLoader.access$100(URLClassLoader.java:56) at java.net.URLClassLoader$1.run(URLClassLoader.java:195) at java.security.AccessController.doPrivileged(Native Method) at java.net.URLClassLoader.findClass(URLClassLoader.java:188) at org.apache.catalina.loader.StandardClassLoader.findClass(StandardClassLoader.java:648) at org.apache.catalina.loader.StandardClassLoader.loadClass(StandardClassLoader.java:987) at org.apache.catalina.loader.StandardClassLoader.loadClass(StandardClassLoader.java:906) at org.apache.cocoon.framework.Manager.create(Manager.java:91) at org.apache.cocoon.Engine.(Engine.java:139) at org.apache.cocoon.Engine.getInstance(Engine.java:223) at org.apache.cocoon.Cocoon.init(Cocoon.java:141) at org.apache.catalina.core.StandardWrapper.load(StandardWrapper.java:755) at org.apache.catalina.core.StandardWrapper.allocate(StandardWrapper.java:544) at org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperValve.java:229) at org.apache.catalina.core.ContainerBase.invoke(ContainerBase.java:977) at org.apache.catalina.core.StandardContextValve.invoke(StandardContextValve.java:165) at org.apache.catalina.core.ContainerBase.invoke(ContainerBase.java:977) at org.apache.catalina.core.StandardContext.invoke(StandardContext.java:1876) at org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:161) at org.apache.catalina.valves.ValveBase.invokeNext(ValveBase.java:242) at org.apache.catalina.valves.AccessLogValve.invoke(AccessLogValve.java:343) at org.apache.catalina.core.ContainerBase.invoke(ContainerBase.java:975) at org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineValve.java:159) at org.apache.catalina.core.ContainerBase.invoke(ContainerBase.java:977) at
Re: [ANNOUNCE] Tomcat 4.0 Milestone 4 - cocoon security problem?
Ray Allis wrote: "Craig R. McClanahan" wrote: We're pleased to announce the availabililty of milestone 4 of the Tomcat 4.0 servlet container and JSP engine. Compared to milestone 3, this release reflects the following changes: Come and get it! Got it! Ooops! I lost cocoon! Groan ... BOY do I hate class loaders :-) Could you try me an experiment? * Comment out the servlet declaration for the JSP servlet in $CATALINA_HOME/conf/web.xml * Temporarily remove "crimson.jar" and "jaxp.jar" from $CATALINA_HOME/lib * Restart and see if Cocoon works The right long term answer is that Xerces becomes JAXP-1.1 compatible, so that system administrators can simply use that instead of Crimson if they want to. In the mean time, Jasper (the JSP servlet) has a requirement for Crimson because it is the only JAXP-1.1 compatible parser available (we needed the portable SAX2 support). If you need Cocoon *and* JSP, I don't have a good answer for you right at the moment ... Craig McClanahan
[ANNOUNCE] Tomcat 4.0 Milestone 4
We're pleased to announce the availabililty of milestone 4 of the Tomcat 4.0 servlet container and JSP engine. Compared to milestone 3, this release reflects the following changes: * Implementation of all the changes between "public draft" and "proposed final draft" of the Servlet 2.3 and JSP 1.2 specifications. * Implementation of all remaining 2.3 / 1.2 features -- Tomcat 4.0 is now a feature complete implementation of the new specs! * Many bug fixes (see RELEASE-NOTES-4.0-M4.txt in the top level directory). Binary distributions of the new release are available from: http://jakarta.apache.org/builds/jakarta-tomcat-4.0/release/v4.0-m4 and source releases can be downloaded from: http://jakarta.apache.org/builds/jakarta-tomcat-4.0/release/v4.0-m4/src If you are planning on building Tomcat 4.0-m4 from source, you will want to pick up the corresponding distribution of the servlet API classes, found in the same directory. Users of the binary distribution need not do this -- a servlet.jar file containing the most current version of the servlet API classes is included in the "bin" directory of the binary release. Come and get it! Craig McClanahan
RE: [ANNOUNCE] Tomcat 4.0 Milestone 4
-Original Message- From: Craig R. McClanahan [mailto:[EMAIL PROTECTED]] Sent: Thursday, November 02, 2000 10:07 AM To: [EMAIL PROTECTED]; [EMAIL PROTECTED]; [EMAIL PROTECTED]; [EMAIL PROTECTED] Subject: [ANNOUNCE] Tomcat 4.0 Milestone 4 We're pleased to announce the availabililty of milestone 4 of the Tomcat 4.0 servlet container and JSP engine. Compared to milestone 3, this release reflects the following changes: * Implementation of all the changes between "public draft" and "proposed final draft" of the Servlet 2.3 and JSP 1.2 specifications. * Implementation of all remaining 2.3 / 1.2 features -- Tomcat 4.0 is now a feature complete implementation of the new specs! * Many bug fixes (see RELEASE-NOTES-4.0-M4.txt in the top level directory). Binary distributions of the new release are available from: http://jakarta.apache.org/builds/jakarta-tomcat-4.0/release/v4.0-m4 and source releases can be downloaded from: http://jakarta.apache.org/builds/jakarta-tomcat-4.0/release/v4.0-m4/src If you are planning on building Tomcat 4.0-m4 from source, you will want to pick up the corresponding distribution of the servlet API classes, found in the same directory. Users of the binary distribution need not do this -- a servlet.jar file containing the most current version of the servlet API classes is included in the "bin" directory of the binary release. Come and get it! Craig McClanahan
