I have looked at JSR 77, but not in depth. I am all for instrumenting Tomcat using JMX where it makes sense.
And will help when/if I have time. Glenn Costin Manolache wrote:
JSR77 defines a certain model - in particular a WebModule must
include an attribute "servlets[]" that lists all the servlets
in the webapp, and it also requires on JMX mbean per servlet.
( tomcat uses that to provide all kind of performance and statistical info ).
The problem is - JSPs are not visible, since Jasper creates them
internally. One solution is to turn JspServletWrapper into
an interface, with a GenericServletWrapper impl ( the current code )
and a mechanism to create container-specific wrappers. A TomcatServletWrapper can hook JSP servlets into JMX and
it may also provide future tomcat-specific optimizations ( like
bypassing JspServlet - by registering the ServletWrapper directly into the mapper ).
Questions:
- do we want to do that ( there is some extra complexity and some
work ) ? Does anyone care about JSR77 support in tomcat ?
- where should TomcatServletWrapper live - jasper can have an optional
dependency on catalina, or catalina can have an optional dependency on
jasper.
- should we extend JMX support to other jasper components - to report
things like compilation times, tag pool usage, tag usage, etc ?
- anyone willing to help, or I'm alone :-) ?
Costin
--
To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]>
For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>
-- ---------------------------------------------------------------------- Glenn Nielsen [EMAIL PROTECTED] | /* Spelin donut madder | MOREnet System Programming | * if iz ina coment. | Missouri Research and Education Network | */ | ---------------------------------------------------------------------- -- To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]> For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>
