You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@geronimo.apache.org by "Anita Kulshreshtha (JIRA)" <de...@geronimo.apache.org> on 2006/02/12 01:41:28 UTC

[jira] Updated: (GERONIMO-1035) tomcat integration should wrap each servlet indiviudally

     [ http://issues.apache.org/jira/browse/GERONIMO-1035?page=all ]

Anita Kulshreshtha updated GERONIMO-1035:
-----------------------------------------

    Attachment: tomcat.patch
                tomcat-builder.patch

Updated the  patches, built against trunk (rev 376797). These patches work   with 5.5.12!
1. tomcat-builder.patch - 
  The tomcat-module-builder.patch and TomcatServletHolder from   tomcat.patch is required for this issue.
   Added unit test for G-1585 (securing with /*). This test will fail   unless change from G-1585 is included.
2. tomcat.patch - 
  The  tomcat.patch is needed for stats and should be applied with   management.patch.
3. stats.zip - 
- stats.zip has a JMXPROXY servlet. I think it is a good thing to have in the code base. It lets you peek into tomcat MBeans. We might need   this when we start worrying about the performance issues of the  cluster.   It is a modified version of the one used by tomcat  Manager application.

> tomcat integration should wrap each servlet indiviudally
> --------------------------------------------------------
>
>          Key: GERONIMO-1035
>          URL: http://issues.apache.org/jira/browse/GERONIMO-1035
>      Project: Geronimo
>         Type: New Feature
>   Components: Tomcat
>     Versions: 1.0-M5
>  Environment: All
>     Reporter: Anita Kulshreshtha
>     Assignee: Jeff Genender
>      Fix For: 1.1
>  Attachments: geronimo-stats-1.1-SNAPSHOT.war, management.patch, stats.zip, tomcat-builder.patch, tomcat-builder.patch, tomcat-builder.patch, tomcat.patch, tomcat.patch
>
> TomcatModuleBuilder should wrap each servlet specified in the deployment descriptor individually. This is needed by JSR-77 and for gathering tomcat internal statistics.   

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
   http://issues.apache.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see:
   http://www.atlassian.com/software/jira