Bill Barker wrote:
----- Original Message -----
From: "Henri Gomez" <[EMAIL PROTECTED]>
To: "Tomcat Developers List" <[EMAIL PROTECTED]>
Sent: Wednesday, February 25, 2004 4:04 AM
Subject: Re: [ANN] Apache Tomcat 3.3.2 Release Candidate 1



Bill Barker wrote:


----- Original Message -----
From: "Henri Gomez" <[EMAIL PROTECTED]>
To: "Tomcat Developers List" <[EMAIL PROTECTED]>
Sent: Tuesday, February 24, 2004 7:46 AM
Subject: Re: [ANN] Apache Tomcat 3.3.2 Release Candidate 1




Henri Gomez wrote:


Bill Barker wrote:



The Tomcat Team announces the immediate availability of Apache Tomcat
3.3.2 Release Candidate 1.

Downloads: http://www.apache.org/~larryi/tomcat-3.3.2-rc1

The Apache Tomcat Team


I make test on it and play with JMXSupport and noticed :

- XSL problem with HTTP connector :

[Error] common.xsl:14:80: Element type "xsl:stylesheet" must be

declared.



[Error] common.xsl:16:38: Element type "xsl:import" must be declared.
[Error] common.xsl:19:35: Element type "xsl:param" must be declared.
[Error] common.xsl:21:96: Element type "xsl:variable" must be declared.
[Error] common.xsl:24:28: Element type "xsl:template" must be declared.
[Error] common.xsl:25:30: Element type "xsl:if" must be declared.

....

It seems Costin patch the xsl sometimes ago at mx4j, so should we
included this modified version ?


- 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 ?

org.apache.coyote.tomcat3.CoyoteInterceptor2 didn't present many informations via JMX, could we use a trick to present what is present in processor class ?



I haven't looked at JMXSupport in a while, but it should be possible to

add


this in. o.a.jk and o.a.c.http11 already have the self-registration

code.


It's just a matter of triggering it.

I could do it but wonder where to put the registration, org.apache.coyote.tomcat3.Coyote2 ?



For 3.3.3 that is probably a good place for it.  However, I'm not very happy
about introducing a dependancy on c-m into the Connector this late in the
release cycle.  I'll stick it into JMXSupport for now, and we can re-visit
JMX in 3.3 again after the release (assuming that there is still interest
:).

I'd like to have it of course :)




---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]



Reply via email to