tomcat-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Larry Isaacs" <Larry.Isa...@sas.com>
Subject RE: [POLL] Tomcat 3.3.2 updates
Date Mon, 23 Sep 2002 19:09:12 GMT
Hi Henri,

I would prefer to minimize the impact of upgrading from
3.3.1 to 3.3.2.  I agree with Costin that using 4 with
documentation on the steps to enable the MxInterceptor
would be a resonable way to implement this.

Cheers,
Larry

> -----Original Message-----
> From: Henri Gomez [mailto:hgomez@apache.org] 
> Sent: Monday, September 23, 2002 10:02 AM
> To: tomcat-dev@jakarta.apache.org
> Subject: [POLL] Tomcat 3.3.2 updates
> 
> 
> Hi to all,
> 
> If you tracked the discussion about MxInterceptor and it's
> use in Tomcat 3.3.2-dev you should know that we have some
> modification to Tomcat 3.3.2 jars layout to be able to
> use MxInterceptor :
> 
> 1) mx4j and mx4j-tools should goes in lib/common
> 
> 2) mx4j-tools HTTP adaptor require TRAX (xalan),
>     so we should put in common/lib JAXP+XML PARSER+TRANSFORMER,
>     and as such could use :
> 
>     xerces-j2 2.1.0
>     xalan-j2 2.4.0
>     xml-commons-apis 1.0
> 
>     Since these jars will be in lib/common, users won't be able
>     to use another one for it's own apps.
> 
> 3) We'll have to remove JAXP/XML-PARSER for lib/container.
> 
> 
> Thanks to give your opinion here.
> 
> [ ] 1. Don't care about MBeans, or do want to be able to have
>         different XML apis for apps and container, so keep the
>         current situation.
> 
> [ ] 2. MxInterceptor is really needed, ok to change the layout,
>         we'll warn users in Changelog / Readme
> 
> [ ] 3. I'd like to MxInterceptor and old layout, I'd rather like to
>         have a copy of DynamicMBeanProxy from jtc/util located in
>         a location compatible with container/lib (to be in
>         container_util.jar we could copy it in 
> org.apache.tomcat.util.mx)
> 
> [ ] 4. I'd like to use MxInterceptor, keep the old layout, but don't
>         want to make the copy and could provide some code to 
> avoid that.
> 
> 
> Personally, I'd like solution 4 (but don't know how to), so I'll be 
> pragmatic and retains 3.
> 
> 
> 
> 
> 
> --
> To unsubscribe, e-mail:   
> <mailto:tomcat-dev-> unsubscribe@jakarta.apache.org>
> For 
> additional commands, 
> e-mail: <mailto:tomcat-dev-help@jakarta.apache.org>
> 
> 

--
To unsubscribe, e-mail:   <mailto:tomcat-dev-unsubscribe@jakarta.apache.org>
For additional commands, e-mail: <mailto:tomcat-dev-help@jakarta.apache.org>


Mime
View raw message