Hello, I understood what the problem was. Sorry for the disturbance.
For future readers : The 'defaut' config contains file jbossjca-service.xml which declares the CachedConnectionManager MBean. Furthermore, JBoss deploys sar files BEFORE *-service.xml files. See Wiki. This fully explains why the MBean inside the sar file could not put a dependance on the CachedConnectionManager MBean without an error. I changed my deployment order and made sure that the sar file is deployed last. Fred View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=3885699#3885699 Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=3885699 ------------------------------------------------------- SF.Net email is sponsored by: Discover Easy Linux Migration Strategies from IBM. Find simple to follow Roadmaps, straightforward articles, informative Webcasts and more! Get everything you need to get up to speed, fast. http://ads.osdn.com/?ad_id=7477&alloc_id=16492&op=click _______________________________________________ JBoss-user mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/jboss-user
