You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@tomcat.apache.org by Henri Gomez <hg...@apache.org> on 2002/09/23 16:01:44 UTC
[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: <ma...@jakarta.apache.org>
For additional commands, e-mail: <ma...@jakarta.apache.org>
Re: [POLL] Tomcat 3.3.2 updates
Posted by Costin Manolache <cm...@yahoo.com>.
Henri Gomez wrote:
> 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.
>
> [+0] 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.
I care about MBeans, but we can keep the current situation as
stable and copy xerces, xalan, etc in common/ for mx experiments.
> [ ] 2. MxInterceptor is really needed, ok to change the layout,
> we'll warn users in Changelog / Readme
It is needed - for experiments and to enahance the module. Right
now it's not very usefull without ability to save and with the
limited visibility ( i.e. very few info is available ).
As we implement the proposed JNDI/JMX config ( for 5.0 - but will work
with any tomcat in the same way ) - MxInterceptor will become essential
( for 3.x ). However when we implement the new coyote hooks, if all goes
as planned ( and Interceptor/Valve will be particular cases of the new
hooks ) then MxInteceptor will not be needed.
> [ ] 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)
That's possible - but given 5.0 I think it would be waste of time.
> [ ] 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.
+1
Costin
>
>
> Personally, I'd like solution 4 (but don't know how to), so I'll be
> pragmatic and retains 3.
--
Costin
--
To unsubscribe, e-mail: <ma...@jakarta.apache.org>
For additional commands, e-mail: <ma...@jakarta.apache.org>
Re: [POLL] Tomcat 3.3.2 updates
Posted by Bojan Smojver <bo...@rexursive.com>.
On Tue, 2002-09-24 at 00:01, Henri Gomez wrote:
> Thanks to give your opinion here.
>
> [X] 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.
However, as long as I can:
1. Disable it completely in server.xml
2. Remove unwanted XML parser JAR's manually
I'm OK with any, really.
Bojan
--
To unsubscribe, e-mail: <ma...@jakarta.apache.org>
For additional commands, e-mail: <ma...@jakarta.apache.org>
AW: [POLL] Tomcat 3.3.2 updates
Posted by Hans Schmid <Ha...@einsurance.de>.
Hi,
since our application uses TopLink, we can not upgrade to xerces 2.
There are hardcoded xerces 1 classes used directly from TopLink.
So 2) is a showstopper for all people with 3rd party jars requiring xerces 1
MBeans are useful for us, but not required. We are already using mx4j and
mx4j-tools in our webapp together with xerces 1.4.0 and xalan 2.1.0
My preference would be. Leave it as it is, but give a short
readme hat to copy where to be abe to use MxInterceptor
Thanks,
Hans
> -----Ursprungliche Nachricht-----
> Von: Henri Gomez [mailto:hgomez@apache.org]
> Gesendet: Montag, 23. September 2002 16:02
> An: tomcat-dev@jakarta.apache.org
> Betreff: [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:
<ma...@jakarta.apache.org>
For additional commands, e-mail: <ma...@jakarta.apache.org>
--
To unsubscribe, e-mail: <ma...@jakarta.apache.org>
For additional commands, e-mail: <ma...@jakarta.apache.org>