I think you guys are thinking in purely JEE terms, in which case you are probably
correct.
But what abou people who use JBoss as an all purpose service hosting container and
aren't doing JEE - it would nice for them to be able to use recovery too.
For instance, JBM has a messaging bridge - which can run standalone in basically a
stripped down version of JBoss. The bridge creates connections to other jms servers, and
(depending on QoS required) consumes and send messages from one server to the other in a
JTA transaction.
No JCA is used here, but we need recovery. So far we have done this by implementing our
own XAResourceRecovery.
And you can imagine many more cases where people implement their own non JEE services
which do stuff with XA not using JCA.
So, yes, I admit that from inside the JEE app server, all XA stuff should be done via JCA,
but should we limit ourselves to that?
Why not abstract out the recovery stuff to another service which can be used by both JCA
and anyone else?
View the original post :
http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4006041#...
Reply to the post :
http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&a...