[jboss-dev-forums] [Design of JCA on JBoss] - Re: JBossTS/JBossJCA XA/Local transactions
mark.little@jboss.com
do-not-reply at jboss.com
Tue Nov 28 11:03:34 EST 2006
This came in just as I hit submit on my last post.
"weston.price at jboss.com" wrote : 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.
|
Sure. If you don't support recovery then it doesn't make any difference.
anonymous wrote :
| 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.
|
I don't think we're in disagreement about the fact that there are different implementations of one-phase aware resources. It's whether or not more than one of them occurs in the same transaction often enough to warrant a solution within the code, or whether or not it's more a restructuring of the user's application to get them better failure semantics.
anonymous wrote :
| 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.
|
Unfortunately there's a real 're-education' situation on our hands anyway. JBossTS is significantly different from JBossTM. This is only one area.
anonymous wrote :
| Again, the cost thing is a factor as well. In many situations, XA costs and many times this does not come cheap.
|
ACID transactions aren't cheap. I'm not going to go into this again though.
anonymous wrote :
| 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.
|
For 4.0.x we are supporting both. For 5.0 we only support JBossTS. If there are any real use cases for this that can't be ignored, then we can deal with the situation then.
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3989378#3989378
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=3989378
More information about the jboss-dev-forums
mailing list