On 2003.06.22 23:26 Brian Wallis wrote: > On Fri, 20 Jun 2003 22:41, David Jencks wrote: > > Could I ask what you are using the value for? JBoss doesn't use this > info > > at all and at least the Integer attribute is not present in JBoss 4 > > (probably not the original string either). The best solution might be > to > > have the attribute return the String, although this might cause > backwards > > compatibility issues. > > To determine the transaction support level of the RA. > > I realise that JBoss doesn't configure transactions via this method, > using the > *-service.xml to configure the container, but the value in the deployment > > descriptor should be correct and is a mandatory attribute. I suspect > JBoss > should probably check that the configuration of the connection manager > and > what is specified in the deployment descriptor are the same. > > I agree that returning the string value probably makes more sense. (I > also > noticed that the comments in the DTD on the allowed values is not > correct, it > reflects the pre-1.0 DTD for RAs) > > Is there a better way to determine the transaction support level? I have > a > session bean that uses a bunch of resource adapters. Some of them support > > transactions and some don't. I have a list of the names of the RAs I'm > going > to talk to during a transaction so rather than find out with an error > halfway > through a transaction, I'd like to determine if all the RAs in the list > support transactions before I start.
You could look at the class of the connection manager mbean, which you can obtain via jmx (ObjectInstance). The level of tx support the adapter is deployed with seems to me to be more relevant than the level it supports. (For instance, theoretically at least, an xa-supporting adapter can be deployed with local tx or no tx support). The only use I can think of for this attribute at runtime is if your program is generating *-ds.xml's to deploy dynamically and needs to guess the proper cm to use. I'm having a hard time imagining a situation where this would be appropriate and the desired level of tx support was not available. You shouldn't get any errors no matter what the tx support is, provided that all ra's are deployed appropriately. Of course, unless they all support xa transactions you are liable to get unrecoverable inconsistencies in case of failure during commit. david jencks > > brian wallis... > > > > ------------------------------------------------------- > This SF.Net email is sponsored by: INetU > Attention Web Developers & Consultants: Become An INetU Hosting Partner. > Refer Dedicated Servers. We Manage Them. You Get 10% Monthly Commission! > INetU Dedicated Managed Hosting http://www.inetu.net/partner/index.php > _______________________________________________ > JBoss-user mailing list > [EMAIL PROTECTED] > https://lists.sourceforge.net/lists/listinfo/jboss-user > > ------------------------------------------------------- This SF.Net email is sponsored by: INetU Attention Web Developers & Consultants: Become An INetU Hosting Partner. Refer Dedicated Servers. We Manage Them. You Get 10% Monthly Commission! INetU Dedicated Managed Hosting http://www.inetu.net/partner/index.php _______________________________________________ JBoss-user mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/jboss-user
