Hi, I have created a new post that continues this one
http://www.jboss.org/index.html?module=bb&op=viewtopic&t=154012 because I think this subject describes better what I want to discuss, so if administrators want to delete the old post and continue this one I think it would be better. Basically I want to discuss about how to handle the ManagedConnectionFactory lifecycle I have developed a solution for this issue that I want to share with you to know your impressions. I have modified jboss-jca sources in my jboss installation to do the following: I have added an interface ManagedConnectionFactoryLifeCycle as follows: | public interface ManagedConnectionFactoryLifeCycle { | | public void start(); | | public void stop(); | } | I have added the following code in org.jboss.resource.connectionmanager.RARDeployment | protected void startService() throws Exception | { | ...original actions | | if (mcf instanceof ManagedConnectionFactoryLifeCycle) | { | ManagedConnectionFactoryLifeCycle mcflc = (ManagedConnectionFactoryLifeCycle) mcf; | mcflc.start(); | } | } | | protected void stopService() | { | if (mcf instanceof ManagedConnectionFactoryLifeCycle) | { | ManagedConnectionFactoryLifeCycle mcflc = (ManagedConnectionFactoryLifeCycle) mcf; | mcflc.stop(); | } | ... original actions | } | Then my ManagedConnectionFactory implements this interface and can handle its deployment and undeployment and perform actions needed. It works, but I know this is not JCA compliant, so I would like to know if you agree with this solution or if you can suggest any other better solution. Thanks a lot View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=4225822#4225822 Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=4225822 _______________________________________________ jboss-user mailing list jboss-user@lists.jboss.org https://lists.jboss.org/mailman/listinfo/jboss-user
