Hi,
+1 to explore the idea further. IMO, it will allows any JAX-WS compliant
stack to be plugged into Tuscany for binding.ws. We can support the JAX-WS
from JDK6, CXF, Axis2 without too much tweaks between the different
implementations.
I reactivated the work to use JAX-WS APIs to implement binding.ws in my
sandbox [1] recently. The reference binding is working for a basic sample. I
recently added some code on the service binding side, but I didn't have
chance to bring it up yet.
[1] http://svn.apache.org/repos/asf/tuscany/sandbox/rfeng/binding-ws-jaxws/
Thanks,
Raymond
--------------------------------------------------
From: "Simon Laws" <[email protected]>
Sent: Monday, March 08, 2010 9:54 AM
To: "tuscany-dev" <[email protected]>
Subject: [2.x] binding.ws as a JAX-WS provider/client
Hi
As part of tidying up the web service binding I've been looking at
ways we can more cleanly use Axis APIs/SPs to try and:
1/ insulate ourselves more effectively from future Axis changes
2/ make it easier to plug in other ws stacks
Haven't got very far but am looking at making the Tuscany chain a
JAX-WS service provider on the service side. The extent of this
exercise to date is limited to pulling the head of the service chain
into a javax.xml.ws.Provider [1] in order to understand the existing
code. The invoke() operation isn't active yet as this is where we jump
off and re-factor the way that the Axis integration is done. I haven't
done anything with the reference side yet.
I notice Raymond was doing some sandbox stuff in this area so it seems
like a good point to pull a design together. Before we start on
technical details can people chime in with what's been done already?
Regards
Simon
[1]
http://svn.apache.org/repos/asf/tuscany/sca-java-2.x/trunk/modules/binding-ws-runtime-axis2/src/main/java/org/apache/tuscany/sca/binding/ws/axis2/provider/Axis2ServiceProvider.java
--
Apache Tuscany committer: tuscany.apache.org
Co-author of a book about Tuscany and SCA: tuscanyinaction.com
