Re: TC 3.3.2 and JMX
Henri Gomez wrote: Bill Barker wrote: - Original Message - From: "Henri Gomez" <[EMAIL PROTECTED]> To: "Tomcat Developers List" <[EMAIL PROTECTED]> Sent: Wednesday, February 25, 2004 4:50 AM Subject: TC 3.3.2 and JMX Any objection to set the default JMX port to -1 ? None here. Jk-Coyote is now the default, and it's connector support is better. Ok, I'll commit tomorrow Bill was faster - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: TC 3.3.2 and JMX
Bill Barker wrote: - Original Message - From: "Henri Gomez" <[EMAIL PROTECTED]> To: "Tomcat Developers List" <[EMAIL PROTECTED]> Sent: Wednesday, February 25, 2004 4:50 AM Subject: TC 3.3.2 and JMX Any objection to set the default JMX port to -1 ? None here. Jk-Coyote is now the default, and it's connector support is better. Ok, I'll commit tomorrow - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: TC 3.3.2 and JMX
- Original Message - From: "Henri Gomez" <[EMAIL PROTECTED]> To: "Tomcat Developers List" <[EMAIL PROTECTED]> Sent: Wednesday, February 25, 2004 4:50 AM Subject: TC 3.3.2 and JMX > Any objection to set the default JMX port to -1 ? > None here. Jk-Coyote is now the default, and it's connector support is better. > - As many, in my web application, I allready load HTTP/JRMP connector > (at special ports with custom login/pwd), but since JMXSupport is > loaded before my app, it didn't use my HTTP port settings. > > What about set port to -1 by default in interceptors.xml to avoid > such problems ? > > > - > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] > This message is intended only for the use of the person(s) listed above as the intended recipient(s), and may contain information that is PRIVILEGED and CONFIDENTIAL. If you are not an intended recipient, you may not read, copy, or distribute this message or any attachment. If you received this communication in error, please notify us immediately by e-mail and then delete all copies of this message and any attachments. In addition you should be aware that ordinary (unencrypted) e-mail sent through the Internet is not secure. Do not send confidential or sensitive information, such as social security numbers, account numbers, personal identification numbers and passwords, to us via ordinary (unencrypted) e-mail. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: TC 3.3.2-dev and endorsed lib
Bill Barker a écrit : - Original Message - From: "Henri Gomez" <[EMAIL PROTECTED]> To: "Tomcat Developers List" <[EMAIL PROTECTED]> Sent: Monday, October 13, 2003 2:09 AM Subject: Re: TC 3.3.2-dev and endorsed lib Bill Barker a écrit : - Original Message - From: "Henri Gomez" <[EMAIL PROTECTED]> To: "Tomcat Developers List" <[EMAIL PROTECTED]> Sent: Monday, October 13, 2003 1:28 AM Subject: TC 3.3.2-dev and endorsed lib In TC 4.1.x and 5.0.x there is support for endorsed lib but nothing like this in tc 3.3.2-dev. Since we may have people (including myself), who will have to use SDK 1.4.x with Tomcat 3.3.2, I like to add such feature to Tomcat 3.3.2-dev. It's not really necessary for 3.3.x, since the XML parsing requirements for Tomcat are pretty limited (without looking, we are currently shipping with a jaxp1.x version I believe). I was thinking put the endorsed in lib/endorsed, ie next to lib/common, lib/apps and lib/container. I'm +0 as long as the lib/endorsed directory is empty in the default install. Otherwise, I'm -1. I'll modify run scripts and build for such feature. If a classloader specialist could see if something is required (from TC 4.1 it seems yes). The Tomcat 3.3 ClassLoaders are all delegating loaders (so it is much simpler than the 4.x/5.x case). If you are using a 1.4.x JVM, Tomcat 3.3 will always grap the XML parser from the System ClassLoader (either the one that ships-with, or the endorsed). Even if we set -Djava.endorsed and fill the directory with the jars we want it to use ? That should work much like it does for 4.1.x/5.0.x (but I haven't tried it :). Once you get out of the WebappClassLoader, the 4.1.x/5.0.x ClassLoaders are delegating CLs. Again, I'm +0 to set the -Djava.endorsed.dir to an empty directory (that the user can copy their favorite xerces version to), and -1 to populate it by default. Ok, I will just create structure but don't populate by default - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: TC 3.3.2-dev and endorsed lib
- Original Message - From: "Henri Gomez" <[EMAIL PROTECTED]> To: "Tomcat Developers List" <[EMAIL PROTECTED]> Sent: Monday, October 13, 2003 2:09 AM Subject: Re: TC 3.3.2-dev and endorsed lib > Bill Barker a écrit : > > > - Original Message - > > From: "Henri Gomez" <[EMAIL PROTECTED]> > > To: "Tomcat Developers List" <[EMAIL PROTECTED]> > > Sent: Monday, October 13, 2003 1:28 AM > > Subject: TC 3.3.2-dev and endorsed lib > > > > > > > >>In TC 4.1.x and 5.0.x there is support for endorsed lib but > >>nothing like this in tc 3.3.2-dev. > >> > >>Since we may have people (including myself), who will have > >>to use SDK 1.4.x with Tomcat 3.3.2, I like to add such feature > >>to Tomcat 3.3.2-dev. > >> > > > > > > It's not really necessary for 3.3.x, since the XML parsing requirements for > > Tomcat are pretty limited (without looking, we are currently shipping with a > > jaxp1.x version I believe). > > > > > >>I was thinking put the endorsed in lib/endorsed, ie next > >>to lib/common, lib/apps and lib/container. > >> > > > > > > I'm +0 as long as the lib/endorsed directory is empty in the default > > install. Otherwise, I'm -1. > > > > > > > >>I'll modify run scripts and build for such feature. > >> > >>If a classloader specialist could see if something is > >>required (from TC 4.1 it seems yes). > > > > > > The Tomcat 3.3 ClassLoaders are all delegating loaders (so it is much > > simpler than the 4.x/5.x case). If you are using a 1.4.x JVM, Tomcat 3.3 > > will always grap the XML parser from the System ClassLoader (either the one > > that ships-with, or the endorsed). > > Even if we set -Djava.endorsed and fill the directory with the jars we > want it to use ? > That should work much like it does for 4.1.x/5.0.x (but I haven't tried it :). Once you get out of the WebappClassLoader, the 4.1.x/5.0.x ClassLoaders are delegating CLs. Again, I'm +0 to set the -Djava.endorsed.dir to an empty directory (that the user can copy their favorite xerces version to), and -1 to populate it by default. > > > - > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] > > This message is intended only for the use of the person(s) listed above as the intended recipient(s), and may contain information that is PRIVILEGED and CONFIDENTIAL. If you are not an intended recipient, you may not read, copy, or distribute this message or any attachment. If you received this communication in error, please notify us immediately by e-mail and then delete all copies of this message and any attachments. In addition you should be aware that ordinary (unencrypted) e-mail sent through the Internet is not secure. Do not send confidential or sensitive information, such as social security numbers, account numbers, personal identification numbers and passwords, to us via ordinary (unencrypted) e-mail. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: TC 3.3.2-dev and endorsed lib
Bill Barker a écrit : - Original Message - From: "Henri Gomez" <[EMAIL PROTECTED]> To: "Tomcat Developers List" <[EMAIL PROTECTED]> Sent: Monday, October 13, 2003 1:28 AM Subject: TC 3.3.2-dev and endorsed lib In TC 4.1.x and 5.0.x there is support for endorsed lib but nothing like this in tc 3.3.2-dev. Since we may have people (including myself), who will have to use SDK 1.4.x with Tomcat 3.3.2, I like to add such feature to Tomcat 3.3.2-dev. It's not really necessary for 3.3.x, since the XML parsing requirements for Tomcat are pretty limited (without looking, we are currently shipping with a jaxp1.x version I believe). I was thinking put the endorsed in lib/endorsed, ie next to lib/common, lib/apps and lib/container. I'm +0 as long as the lib/endorsed directory is empty in the default install. Otherwise, I'm -1. I'll modify run scripts and build for such feature. If a classloader specialist could see if something is required (from TC 4.1 it seems yes). The Tomcat 3.3 ClassLoaders are all delegating loaders (so it is much simpler than the 4.x/5.x case). If you are using a 1.4.x JVM, Tomcat 3.3 will always grap the XML parser from the System ClassLoader (either the one that ships-with, or the endorsed). Even if we set -Djava.endorsed and fill the directory with the jars we want it to use ? - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: TC 3.3.2-dev and endorsed lib
- Original Message - From: "Henri Gomez" <[EMAIL PROTECTED]> To: "Tomcat Developers List" <[EMAIL PROTECTED]> Sent: Monday, October 13, 2003 1:28 AM Subject: TC 3.3.2-dev and endorsed lib > In TC 4.1.x and 5.0.x there is support for endorsed lib but > nothing like this in tc 3.3.2-dev. > > Since we may have people (including myself), who will have > to use SDK 1.4.x with Tomcat 3.3.2, I like to add such feature > to Tomcat 3.3.2-dev. > It's not really necessary for 3.3.x, since the XML parsing requirements for Tomcat are pretty limited (without looking, we are currently shipping with a jaxp1.x version I believe). > I was thinking put the endorsed in lib/endorsed, ie next > to lib/common, lib/apps and lib/container. > I'm +0 as long as the lib/endorsed directory is empty in the default install. Otherwise, I'm -1. > I'll modify run scripts and build for such feature. > > If a classloader specialist could see if something is > required (from TC 4.1 it seems yes). The Tomcat 3.3 ClassLoaders are all delegating loaders (so it is much simpler than the 4.x/5.x case). If you are using a 1.4.x JVM, Tomcat 3.3 will always grap the XML parser from the System ClassLoader (either the one that ships-with, or the endorsed). > > Regards > > > > - > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] > This message is intended only for the use of the person(s) listed above as the intended recipient(s), and may contain information that is PRIVILEGED and CONFIDENTIAL. If you are not an intended recipient, you may not read, copy, or distribute this message or any attachment. If you received this communication in error, please notify us immediately by e-mail and then delete all copies of this message and any attachments. In addition you should be aware that ordinary (unencrypted) e-mail sent through the Internet is not secure. Do not send confidential or sensitive information, such as social security numbers, account numbers, personal identification numbers and passwords, to us via ordinary (unencrypted) e-mail. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
RE: TC 3.3.2
> -Original Message- > From: Henri Gomez [mailto:[EMAIL PROTECTED] > Sent: Tuesday, September 30, 2003 4:23 AM > To: Tomcat Developers List > Subject: Re: TC 3.3.2 > > > Bill Barker a écrit : > > > - Original Message - > > From: "Henri Gomez" <[EMAIL PROTECTED]> > > To: "Tomcat Developers List" <[EMAIL PROTECTED]> > > Sent: Monday, September 29, 2003 2:55 AM > > Subject: TC 3.3.2 > > > > > > > >>Hi to all, > >> > >>I commited the last part of clean imports and started to > take a look > >>at bugzilla where many reports seems still open. > >> > >>What's the strategy now ? > >> > >>Should we close those which seems invalid ? > >> > > > > > > Without looking, I believe that most of the open bugs for 3.3 are > > either for the native connectors (and so are really j-t-c bugs), or > > for the Http10Interceptor (which we are deprecating/removing). Of > > course, most of the 91 open Tomcat 3 bugs are for 3.2.x. > > So we should make the 91 3.2.x bugs as WONTFIX and add a comment that > 3.2.x is deprecated and replaced by 3.3.x Yes, unless the bug is applicable to 3.3.2 and is serious enough to warrant fixing. However, I don't think it's worth a lot of effort to determine if a bug is applicable to 3.3.2. Cheers, Larry > > > - > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] > > - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: TC 3.3.2
Bill Barker a écrit : - Original Message - From: "Henri Gomez" <[EMAIL PROTECTED]> To: "Tomcat Developers List" <[EMAIL PROTECTED]> Sent: Monday, September 29, 2003 2:55 AM Subject: TC 3.3.2 Hi to all, I commited the last part of clean imports and started to take a look at bugzilla where many reports seems still open. What's the strategy now ? Should we close those which seems invalid ? Without looking, I believe that most of the open bugs for 3.3 are either for the native connectors (and so are really j-t-c bugs), or for the Http10Interceptor (which we are deprecating/removing). Of course, most of the 91 open Tomcat 3 bugs are for 3.2.x. So we should make the 91 3.2.x bugs as WONTFIX and add a comment that 3.2.x is deprecated and replaced by 3.3.x - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: TC 3.3.2
- Original Message - From: "Henri Gomez" <[EMAIL PROTECTED]> To: "Tomcat Developers List" <[EMAIL PROTECTED]> Sent: Monday, September 29, 2003 2:55 AM Subject: TC 3.3.2 > Hi to all, > > I commited the last part of clean imports and started to take a look > at bugzilla where many reports seems still open. > > What's the strategy now ? > > Should we close those which seems invalid ? > Without looking, I believe that most of the open bugs for 3.3 are either for the native connectors (and so are really j-t-c bugs), or for the Http10Interceptor (which we are deprecating/removing). Of course, most of the 91 open Tomcat 3 bugs are for 3.2.x. > > - > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] > This message is intended only for the use of the person(s) listed above as the intended recipient(s), and may contain information that is PRIVILEGED and CONFIDENTIAL. If you are not an intended recipient, you may not read, copy, or distribute this message or any attachment. If you received this communication in error, please notify us immediately by e-mail and then delete all copies of this message and any attachments. In addition you should be aware that ordinary (unencrypted) e-mail sent through the Internet is not secure. Do not send confidential or sensitive information, such as social security numbers, account numbers, personal identification numbers and passwords, to us via ordinary (unencrypted) e-mail. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
RE: TC 3.3.2
> -Original Message- > From: Henri Gomez [mailto:[EMAIL PROTECTED] > Sent: Monday, September 29, 2003 5:56 AM > To: Tomcat Developers List > Subject: TC 3.3.2 > > > Hi to all, > > I commited the last part of clean imports and started to take > a look at bugzilla where many reports seems still open. > > What's the strategy now ? I should have my builds running again shortly. I'll try to get the nightly binaries updated and accessible again. > > Should we close those which seems invalid ? +1 I'll help review open bugs. I'm also in favor of WONTFIX any Tomcat 3.2.x related bugs. Larry > > > - > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] > > - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
