[Design of JCA on JBoss] - Re: JBossTS/JBossJCA XA/Local transactions
by mark.little@jboss.com
Why do you believe you need this support? JBossTS, like other commercial-grade/enterprise transaction systems, supports the TWO-PHASE COMMIT protocol. This means participants need to understand the prepare/commit/rollback messages they will get from the coordinator.
Now obviously not ever participant in existance is 2PC-aware. In that case, as with other products such as Tux and CICS, we support LRCO. This allows a single 1-phase aware participant to be enlisted with a two-phase transaction as long as it is handled correctly within the protocol. If it isn't, or if you try to add more than one 1-phase aware participant, then you will potentially end up with non-atomic behaviour. Believe it or not, but that's not a good idea. Heuristic outcomes are bad enough, but at least with them you have durably recorded the results and can attempt some form or resolution, even if manually.
There's a really good book on the subject:
http://www.amazon.com/Java-Transaction-Processing-Implementation-Professi...
So rather than rush into supporting something like this, I'd prefer to see a discussion about why it is needed in the first place. If there's a real need then we can consider it, but definitely a case of caveat emptor!
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3988768#3988768
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=3988768
19 years, 4 months
[Design of JBoss ESB] - Re: ESB configuration
by tfennelly
Hey Kurt.
I like your example config file there - it reads and has a structure which can be validated.
On the other hand, I'd also be interested in seeing what the MC/MK can bring to this. I think doing this type of thing in a way that is consistent with other JBoss products is something that would be nice and a big selling feature. I'd imagine that this would be something that would appeal greatly to existing MC/MK users. Of course, this all assumes that it could meet our needs. Add to this the fact that MC/MK is already there and proven to work. If we didn't use this (e.g. because we wanted to stay "light"), what would we fill the gap with other than something we'd write ourselves i.e. effectively our own "lightweight" container, which we'd have to test, maintain etc. I think it's always easy to underestimate the LOE on something like this.
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3988767#3988767
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=3988767
19 years, 4 months