anonymous wrote : 2)Provide a serializable wrapper to support XA resource recovery using
JBossTS.
|
| It was my plan to use this wrapper both on the inbound and outbound for JCA. From my
understanding, this would enable JBossTS to reconsruct the XAResource and call recover as
the XAResource (in this case the wrapper) would be written to the transaction log enabling
JBossTS to do it's thing.
|
One issue with this is that the user that executed the original transaction may not have
permission to perform a recovery. For instance, only a DBA may have the permission to
perform recovery on the database. Also, because the XA spec is a bit ambiguous,
different XAResources of different vendors may have different requirements on what flags
you pass into XAResource.recover(). There's also the general problem that some
XAResources require Xid padding and others don't. I'm guessing that JBoss TS
solves the latter two problems in very very hacky ways that are easy to break as there is
no defined integration contract between JBoss, JBoss JCA, and Arjuna. I do not know how
or if they solve the permission problem.
View the original post :
http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4005943#...
Reply to the post :
http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&a...