You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@tomcat.apache.org by Marc Saegesser <ma...@apropos.com> on 2001/10/19 19:53:25 UTC
[PROPOSAL] Tomcat 3.2.4 release
I propose that we release the tip of the tomcat_32 branch as Tomcat 3.2.4.
Since the 3.2.3 release there have been several bug fixes and patches
applied to the branch and these should packaged as a public release. I will
be the release manager.
After this release I expect that all future Tomcat 3.x development will be
based on Tomcat 3.3.
The release plan has been checked into cvs and a copy is attached. Please
review the plan reply with your vote.
--------------------------------------------------------------------------
Vote: Tomcat 3.2.4 Release Plan
[ ] +1 I am in favor of the release, and will help support it
[ ] +0 I am in favor of the release, but am unable to help support it
[ ] -0 I am not in favor of the release
[ ] -1 I am against this proposal (must include a reason).
--------------------------------------------------------------------------
Marc Saegesser
Re: [PROPOSAL] Tomcat 3.2.4 release
Posted by Bojan Smojver <bo...@binarix.com>.
Marc Saegesser wrote:
> --------------------------------------------------------------------------
> Vote: Tomcat 3.2.4 Release Plan
> [ ] +1 I am in favor of the release, and will help support it
> [X] +0 I am in favor of the release, but am unable to help support it
> [ ] -0 I am not in favor of the release
> [ ] -1 I am against this proposal (must include a reason).
> --------------------------------------------------------------------------
Bojan
Re: [PROPOSAL] Tomcat 3.2.4 release
Posted by Pier Fumagalli <pi...@betaversion.org>.
Marc Saegesser at marc.saegesser@apropos.com wrote:
> --------------------------------------------------------------------------
> Vote: Tomcat 3.2.4 Release Plan
> [ ] +1 I am in favor of the release, and will help support it
> [X] +0 I am in favor of the release, but am unable to help support it
> [ ] -0 I am not in favor of the release
> [ ] -1 I am against this proposal (must include a reason).
> --------------------------------------------------------------------------
RE: [PROPOSAL] Tomcat 3.2.4 release
Posted by Marc Saegesser <ma...@apropos.com>.
OK, I thought there were changes to Jdk12Interceptor in 3.3 that needed to
be ported back to 3.2.x. If all we need to do is document in server.xml
than that's no problem at all. I'll take care of it.
Marc Saegesser
> -----Original Message-----
> From: costinm@covalent.net [mailto:costinm@covalent.net]
> Sent: Friday, October 19, 2001 3:09 PM
> To: tomcat-dev@jakarta.apache.org
> Subject: RE: [PROPOSAL] Tomcat 3.2.4 release
>
>
> On Fri, 19 Oct 2001, Marc Saegesser wrote:
>
> > Regarging JAXP, if I understand correctly, I can build with and ship the
> > jaxp.jar and crimson.jar from JAXP-1.1 but users can still run with the
> > older jaxp.jar and parser.jar from jaxp-1.0.1, right? I have
> two concerns.
> > First I want to preserve the ability for existing users to
> upgrade to 3.2.4
> > by simply copying the new webserver.jar file into tomcat/lib. Second,
> > because of the class loader issues in 3.2.x, webapps see the
> classes from
> > tomcat/lib before they see the ones in their WEB-INF/lib
> directory. Thus
> > replacing the parser in tomcat/lib could have unintended side effects on
> > existing applications. I don't have any problem shipping with the later
> > JAXP stuff as long as we can still run with the older version that we've
> > shipped with in the past.
>
> Both should work - you can compile with jaxp1.0 and ship with JAXP1.1,
> it's the safest solution. Then it will work out-of-box as before, but will
> be much easier for those who are used to replace the tomcat/lib parser (
> as this step will no longer be needed ). I think those assuming JAXP1.0 is
> present in lib/ is smaller, and they can still use it in lib.
>
> > I'll take a look at the diffs between the Jdk12Interceptor in
> tomcat_32 and
> > 3.3 and how it looks.
>
> No, the Jdk12Interceptor _is_ included in 3.2, as
> org.apache.tomcat.request.Jdk12Interceptor. The only problem is that it is
> not even mentioned in server.xml, and an even bigger problem is that a lot
> of people are having problems with SOAP, jndi, Jaxp - all of them require
> a thread context class loader.
>
> We can only include it commented out, but I think having it in by default
> is even better ( we are still compatible with JDK1.1 - but I think it's
> better to ask 1.1 users to remove it instead of asking 1.2 users
> to add it ).
>
> Costin
RE: [PROPOSAL] Tomcat 3.2.4 release
Posted by co...@covalent.net.
On Fri, 19 Oct 2001, Marc Saegesser wrote:
> Regarging JAXP, if I understand correctly, I can build with and ship the
> jaxp.jar and crimson.jar from JAXP-1.1 but users can still run with the
> older jaxp.jar and parser.jar from jaxp-1.0.1, right? I have two concerns.
> First I want to preserve the ability for existing users to upgrade to 3.2.4
> by simply copying the new webserver.jar file into tomcat/lib. Second,
> because of the class loader issues in 3.2.x, webapps see the classes from
> tomcat/lib before they see the ones in their WEB-INF/lib directory. Thus
> replacing the parser in tomcat/lib could have unintended side effects on
> existing applications. I don't have any problem shipping with the later
> JAXP stuff as long as we can still run with the older version that we've
> shipped with in the past.
Both should work - you can compile with jaxp1.0 and ship with JAXP1.1,
it's the safest solution. Then it will work out-of-box as before, but will
be much easier for those who are used to replace the tomcat/lib parser (
as this step will no longer be needed ). I think those assuming JAXP1.0 is
present in lib/ is smaller, and they can still use it in lib.
> I'll take a look at the diffs between the Jdk12Interceptor in tomcat_32 and
> 3.3 and how it looks.
No, the Jdk12Interceptor _is_ included in 3.2, as
org.apache.tomcat.request.Jdk12Interceptor. The only problem is that it is
not even mentioned in server.xml, and an even bigger problem is that a lot
of people are having problems with SOAP, jndi, Jaxp - all of them require
a thread context class loader.
We can only include it commented out, but I think having it in by default
is even better ( we are still compatible with JDK1.1 - but I think it's
better to ask 1.1 users to remove it instead of asking 1.2 users to add it ).
Costin
RE: [PROPOSAL] Tomcat 3.2.4 release
Posted by Marc Saegesser <ma...@apropos.com>.
Regarging JAXP, if I understand correctly, I can build with and ship the
jaxp.jar and crimson.jar from JAXP-1.1 but users can still run with the
older jaxp.jar and parser.jar from jaxp-1.0.1, right? I have two concerns.
First I want to preserve the ability for existing users to upgrade to 3.2.4
by simply copying the new webserver.jar file into tomcat/lib. Second,
because of the class loader issues in 3.2.x, webapps see the classes from
tomcat/lib before they see the ones in their WEB-INF/lib directory. Thus
replacing the parser in tomcat/lib could have unintended side effects on
existing applications. I don't have any problem shipping with the later
JAXP stuff as long as we can still run with the older version that we've
shipped with in the past.
I'll take a look at the diffs between the Jdk12Interceptor in tomcat_32 and
3.3 and how it looks.
Marc Saegesser
> -----Original Message-----
> From: costinm@covalent.net [mailto:costinm@covalent.net]
> Sent: Friday, October 19, 2001 1:08 PM
> To: tomcat-dev@jakarta.apache.org
> Subject: Re: [PROPOSAL] Tomcat 3.2.4 release
>
>
> +1
>
> Would it be possible to also include a recent Jaxp ( xerces is also
> fine ) and add the Jdk12Interceptor ( that sets context class loader ) in
> the default server.xml ?
> ( with instructions on how to remove it on JDK1.1 ) ?
>
> There are so many SOAP, etc problems that are resolved by just adding the
> module, and only few people knows about this...
>
>
> Costin
>
> On Fri, 19 Oct 2001, Marc Saegesser wrote:
>
>
> > I propose that we release the tip of the tomcat_32 branch as
> Tomcat 3.2.4.
> > Since the 3.2.3 release there have been several bug fixes and patches
> > applied to the branch and these should packaged as a public
> release. I will
> > be the release manager.
> >
> > After this release I expect that all future Tomcat 3.x
> development will be
> > based on Tomcat 3.3.
> >
> > The release plan has been checked into cvs and a copy is
> attached. Please
> > review the plan reply with your vote.
> >
> >
> --------------------------------------------------------------------------
> > Vote: Tomcat 3.2.4 Release Plan
> > [ ] +1 I am in favor of the release, and will help support it
> > [ ] +0 I am in favor of the release, but am unable to help support it
> > [ ] -0 I am not in favor of the release
> > [ ] -1 I am against this proposal (must include a reason).
> >
> --------------------------------------------------------------------------
> >
> >
> > Marc Saegesser
> >
Re: [PROPOSAL] Tomcat 3.2.4 release
Posted by co...@covalent.net.
+1
Would it be possible to also include a recent Jaxp ( xerces is also
fine ) and add the Jdk12Interceptor ( that sets context class loader ) in
the default server.xml ?
( with instructions on how to remove it on JDK1.1 ) ?
There are so many SOAP, etc problems that are resolved by just adding the
module, and only few people knows about this...
Costin
On Fri, 19 Oct 2001, Marc Saegesser wrote:
> I propose that we release the tip of the tomcat_32 branch as Tomcat 3.2.4.
> Since the 3.2.3 release there have been several bug fixes and patches
> applied to the branch and these should packaged as a public release. I will
> be the release manager.
>
> After this release I expect that all future Tomcat 3.x development will be
> based on Tomcat 3.3.
>
> The release plan has been checked into cvs and a copy is attached. Please
> review the plan reply with your vote.
>
> --------------------------------------------------------------------------
> Vote: Tomcat 3.2.4 Release Plan
> [ ] +1 I am in favor of the release, and will help support it
> [ ] +0 I am in favor of the release, but am unable to help support it
> [ ] -0 I am not in favor of the release
> [ ] -1 I am against this proposal (must include a reason).
> --------------------------------------------------------------------------
>
>
> Marc Saegesser
>
RE: [PROPOSAL] Tomcat 3.2.4 release
Posted by cm...@yahoo.com.
On Fri, 19 Oct 2001, Marc Saegesser wrote:
+1
Costin
> I suppose I should vote for my own proposal.
>
> --------------------------------------------------------------------------
> Vote: Tomcat 3.2.4 Release Plan
> [X] +1 I am in favor of the release, and will help support it
> [ ] +0 I am in favor of the release, but am unable to help support it
> [ ] -0 I am not in favor of the release
> [ ] -1 I am against this proposal (must include a reason).
> --------------------------------------------------------------------------
>
> Marc Saegesser
>
RE: [PROPOSAL] Tomcat 3.2.4 release
Posted by Marc Saegesser <ma...@apropos.com>.
I suppose I should vote for my own proposal.
--------------------------------------------------------------------------
Vote: Tomcat 3.2.4 Release Plan
[X] +1 I am in favor of the release, and will help support it
[ ] +0 I am in favor of the release, but am unable to help support it
[ ] -0 I am not in favor of the release
[ ] -1 I am against this proposal (must include a reason).
--------------------------------------------------------------------------
Marc Saegesser