[jboss-jira] [JBoss JIRA] Updated: (JBAS-4511) CachedConnectionManager valve needs enabling in JBoss5

[Remy Maucherat (JIRA)]

     [ http://jira.jboss.com/jira/browse/JBAS-4511?page=all ]

Remy Maucherat updated JBAS-4511:
---------------------------------

    Fix Version/s:     (was:  JBossAS-5.0.0.Beta3)
       Complexity: High

I propose postponing this until after AS 5 (since this tree is supposed to be more or less stable, and the current code works perfectly well). This would most likely include using a new infrastructure to process server.xml and META-INF/context.xml webapp configuration (maybe merged into jboss-web.xml).

> CachedConnectionManager valve needs enabling in JBoss5
> ------------------------------------------------------
>
>                 Key: JBAS-4511
>                 URL: http://jira.jboss.com/jira/browse/JBAS-4511
>             Project: JBoss Application Server
>          Issue Type: Task
>      Security Level: Public(Everyone can see) 
>          Components: Web (Tomcat) service
>    Affects Versions: JBossAS-5.0.0.Beta2
>            Reporter: Adrian Brock
>         Assigned To: Remy Maucherat
>
> The CCM valve needs enabling in JBoss5.
> However, you can no longer just enable due to the issue described on the forum thread.
> I've temporarily moved the CachedConnectionManager MBean into deployers
> so Tomcat can depend it, but Tomcat should not be in the deployers.
> Once Tomcat is fixed, the file deployers/jca-hack-for-tomcat-service.xml needs removing
> and the FIXMEs in build/build-distr.xml and jbossjca-service.xml reverting.

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