anonymous wrote :
| I disagree.
|
| Let's take the example of JBM for a minute. We already have a recovery mechanism
in place (we use an XAResourceRecovery instance).
|
That's fine. In this case, because you implemented XAResourceRecovery, you are able to
integrate with JBossTS directly. This is the situation you control...all fine well and
good.
Now, how about for XAResources you don't control? How about Oracle, DB2, WebSphereMQ,
etc. What about those?
How do you think these XAResource get enlisted in a transaction to begin with and who
provides access to them? Guess what, it's JCA. ResourceManagers (JMS, JDBC or
otherwise) are managed in an EE environment via JCA. Because JCA is a generic framework
for resource integration use of the underlying XAResource is governed by this framework.
There is no concept of a standalone ResourceManager in an EE environment without an
associated JCA resource adapter...well, other than in the case where the person is just
blatantly attempting to do something wrong, Aunt Doris or otherwise.
For your fundamental disagreement to hold water, you would effectively have to remove JCA
from the equation all together and assume that the Tx Manager has direct access the
underlying XAResources/ResourceManagers *without* JCA intervention. This is simply not the
case and will never be the case in our Application server, or any compliant EE application
server for that matter.
View the original post :
http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4005980#...
Reply to the post :
http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&a...