On 10/18/2010 04:27 AM, Robert Liguori wrote:
Any plans for CXF to support the following?
Enabling atomic transactions (WS-Coordination, WS-AtomicTransactions)
WS-MetadataExchange
How about these:
WS-Eventing
WS-Business Activity
Or this directly?
WS-Notification
Apologies for the delay in replying -- I was in purdah planning the next
6 months work from Monday until today.
First thing: it is possible (indeed straightforward) to use JBoss XTS,
our implementation of the WS-C, WS-AT and WS-BA protocols, with CXF if
you deploy your app inside a JBoss 5.0 and 6.0 application server.
Actually, both these protocols are supported in the latest EAP 5.0
product release.
Second thing: I have recently been working with Mauro Molinari, a member
of the JBossTS/CXF community to make it simple to deploy JBossTS (the
core transaction manager) and JBoss XTS bundled standalone with CXF --
i.e. you do not need to deploy your app to a JBoss app server in order
to use the TS/XTS capabilities. The 4.13 release we produced last week
was missing a few minor tweaks needed to make this trivial to achieve.
These tweaks have now been applied in XTS trunk (see the JBossTS project
repo for the sources) and will be available as a binary download in the
4.14 release which is scheduled for delivery 8 weeks from now. Obviously
this is a community only option.
Third thing: WS-AT and WS-BA clients normally need to expose a service
endpoint in order to be able to complete a transaction (i.e. execute
commit or rollback in the case of WS-AT and execute close or cancel in
the case of WS-BA). This may sound counter-intuitive but that's what the
specs mandate -- the commit-committed exchange is implemented as two
independent oneway message exchanges. This is no great hassle if your
client is running in a container like JBoss AS but it complicates life
if you want your client to just be a simple Java app.
So, I have included an option in the latest XTS implementation which
breaks spec compliance in this one regard, allowing clients to use a
simple request-response exchange to perform completion operations. This
means that the client only needs to rely on HTTP client capability,
avoiding the need to open a public facing socket on the client host,
enable firewall access etc. So, lightweight WS-T clients 'R' us :-)
Obviosuly, once again, this is a community-only option but I am hoping
that we can get the spec fixed in the WSTX committee so that this
becomes a standard option and we can support it.
regards,
Andrew Dinn
-----------
JBoss XTS project lead
