On Mon, Mar 8, 2010 at 6:01 PM, Raymond Feng <[email protected]> wrote: > 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/
Just took a look at the code in your sandbox. On the service side there is a JAX-WS provider similar to the one a referenced earlier in the thread. You've taken it further and registered the provider as a JAX-WS endpoint. I'd like to try this in trunk by adding a new service binding provider to effect this registration. I'm particularly interested in whether this approach presents any restrictions on our ability to configure the binding in terms of transports or policy. Only way to really find out is to try it;-) Haven't looked at the client side yet. Regards Simon
