This content has been marked as final.
Show 5 replies
-
1. Re: OASIS WS-TX v1.1
jhalliday Jul 10, 2007 10:07 AM (in response to ruthbd)We already have a 1.1 implementation, but getting it to work alongside the 1.0 version is tricky. We have yet to decide if the next release will attempt to support both versions or will move exclusively to 1.1. We'll be looking at this in more depth once JBossWS 2.1 is available in August.
-
2. Re: OASIS WS-TX v1.1
ruthbd Jul 10, 2007 10:09 AM (in response to ruthbd)"jhalliday" wrote:
We already have a 1.1 implementation, but getting it to work alongside the 1.0 version is tricky. We have yet to decide if the next release will attempt to support both versions or will move exclusively to 1.1. We'll be looking at this in more depth once JBossWS 2.1 is available in August.
Sounds good, thanks. Could you briefly summarize the salient differences? Or are they just little nits (that make it hard to stay compatible, of course). -
3. Re: OASIS WS-TX v1.1
marklittle Jul 10, 2007 10:19 AM (in response to ruthbd)We spent 18 months moving from 1.0 to 1.1. Check out the public OASIS mailing lists and docs. The changes aren't "nits" ;-)
-
4. Re: OASIS WS-TX v1.1
ruthbd Jul 10, 2007 10:49 AM (in response to ruthbd)"mark.little@jboss.com" wrote:
We spent 18 months moving from 1.0 to 1.1. Check out the public OASIS mailing lists and docs. The changes aren't "nits" ;-)
Sorry, Mark - didn't mean to disparage the effort. I'm just trying to get a handle on what impact the 1.1 stuff might have on our effort to get end-to-end transactions working. -
5. Re: OASIS WS-TX v1.1
marklittle Jul 10, 2007 12:23 PM (in response to ruthbd)"ruthbd" wrote:
"mark.little@jboss.com" wrote:
We spent 18 months moving from 1.0 to 1.1. Check out the public OASIS mailing lists and docs. The changes aren't "nits" ;-)
Sorry, Mark - didn't mean to disparage the effort. I'm just trying to get a handle on what impact the 1.1 stuff might have on our effort to get end-to-end transactions working.
It shouldn't have any impact on e2e tx. It just means that 1.0 and 1.1 are not interoperable directly.