The problem as I see it is in terms of the types of configurations/deployments we have
today. Unfortunatley, the use of multiple 1PC resources in JBoss is quite common, in fact,
I would go so far as to assert this is the *main* type of configuration we see in client
deployments.
This is especially true in the area of JMS where the underlying provider is not required
to support XA. Further, there are a variety of JDBC resources (some of the more off beat
ones) that don't provide XA adapters either.
If we are indeed saying that we no longer support this, or at the very least, it is not
supported with JBossTS then we have a real 're-education' situation on our hands.
This is independent of what is *correct* being that we provided this behavior before no
matter how broken it may have been.
Again, the cost thing is a factor as well. In many situations, XA costs and many times
this does not come cheap. Of course they always have the option to use JBossTM, but I
don't think we want to be in the business of recommending this.
View the original post :
http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3989366#...
Reply to the post :
http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&a...