-
1. Re: confusion about the package structure of XTS
marklittle Jan 23, 2007 3:48 AM (in response to mysl)In order to use WS-TX you do not need to use WS-CAF. All of the jars shipped will be needed though. Please refer to the Programmers Guide for more details, along with the worked demo. If you find issues with the documentation, let us know so we can address them. Thanks.
-
2. Re: confusion about the package structure of XTS
mysl Jan 23, 2007 9:59 PM (in response to mysl)ok, Thanks although I am still confused :-). Actually I have already read the programming guide and run the demo, but I am more curious about the inner architecture. Anyway, Thanks again!
-
3. Re: confusion about the package structure of XTS
odin69 Jan 23, 2008 6:25 AM (in response to mysl)Hello,
Right now I am also a little bit confused about the WS-CAF in the XTS. In the post http://www.jboss.com/index.html?module=bb&op=viewtopic&t=120042
it says that the WS-CAF is no longer supported. so it is correct to say that the XTS only supports ws-tx?
thanks in advance -
4. Re: confusion about the package structure of XTS
marklittle Jan 23, 2008 6:52 AM (in response to mysl)Yes, that's correct.
-
5. Re: confusion about the package structure of XTS
odin69 Jan 23, 2008 7:48 AM (in response to mysl)Ok, so the way of my understanding right now both specifications the ws-tx and the ws-caf are implmented in the jars of the xts, but only the concept of the ws-tx is used by the xts although you need all the jars to make the xts operational, right? So is there any reason why the ws-caf is not supported and is the interoperability based on the ws-tx? So I have read the Programming Guideline but I haven't seen any hints regarding the ws-caf, so are there any documents about the development of ws-caf in jboss?
thanks -
6. Re: confusion about the package structure of XTS
marklittle Jan 23, 2008 3:11 PM (in response to mysl)WS-CAF was supported when this was being done within Arjuna. The core code still remains (WS-CAF had better transaction support than WS-TX), but the SOAP stack is no longer available.