[
http://jira.jboss.com/jira/browse/JBAS-5346?page=all ]
Brian Stansberry updated JBAS-5346:
-----------------------------------
Description: Move the jboss.jca:service=CachedConnectionManager back into deploy, and
move the dependency from the WarDeployer to the jboss.web:service=WebServer mbean. (was:
Move the jboss.jca:service=CachedConnectionManager back into deploy, and move the
dependency from the WarDeployer to the jboss.web:service=WebServer mbean.
The CachedConnectionManager is currently in a file named jca-hack-for-tomcat-service.xml.
I'm taking the liberty of renaming it cached-connmgr-service.xml since it's now
the only mbean in the file. The old 4.x name of jbossjca-service.xml seems overly broad
since all the other services are gone.)
Removed business about renaming the jca-hack-... file, as it was totally wrongheaded.
Just needed to delete the file and uncomment the bean in the regular
jbossjca-service.xml.
Move the CachedConnectionManager back into deploy
-------------------------------------------------
Key: JBAS-5346
URL:
http://jira.jboss.com/jira/browse/JBAS-5346
Project: JBoss Application Server
Issue Type: Task
Security Level: Public(Everyone can see)
Components: Web (Tomcat) service, JCA service
Reporter: Brian Stansberry
Assigned To: Brian Stansberry
Fix For: JBossAS-5.0.0.CR1
Move the jboss.jca:service=CachedConnectionManager back into deploy, and move the
dependency from the WarDeployer to the jboss.web:service=WebServer mbean.
--
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