The current solution of depending on the JcaXAResourceWrapper class located inside the JCA
implementation will not work over time. The current class in AS-5.0 is called
XAResourceWrapper, but provides the same functionality as the old JcaXAResourceWrapper
class.
I think that we should put the wrapper classes (XAResourceWrapper / XidWrapper (JcaXid))
in the JCA SPI, so you can depends on them there.
We could include some basic information in the XAResourceWrapper that would identify which
resource archive the recovery currently is processing - like the EISProductName and
EISProductVersion for starters.
Later on we can provide facilities in the JCA SPI to request more information about the
XAResource or the Xid -- like getJNDIName(XAResouce) and getJNDIName(Xid). But I want to
take a deeper look at the implementation of these methods before committing the project to
implement them.
The first part of the post I could commit after the AS-5.0.CR1 release if you think it
would benefit the users.
View the original post :
http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4159834#...
Reply to the post :
http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&a...