On Wed, Jan 19, 2011 at 10:37 PM, Urso Wieske <[email protected]> wrote: > Hi Gang > I had problems with jax-ws ri. I switched to axis2. May be it's wise for you > to consider using axis2. I discovered that my callbacks were not being > injected by the SCA runtime. > Kind regards > Urso > > Sent from my iPhone > On 19 jan. 2011, at 21:48, "Yang, Gang CTR US USA" <[email protected]> > wrote: > > Classification: UNCLASSIFIED > Caveats: NONE > > Hi, > > > > I noticed in Tusncay 2.0.Beta1 sources distribution, there’re > binding-ws-runtime-jaxws and binding-ws-runtime-jaxws-ri modules, but can’t > find any documentation or discussion about them. Does this mean Tuscany 2.0 > supports JAX-WS? Is it completed? How do I use it? > > > > Thanks, > > Gang > > Classification: UNCLASSIFIED > Caveats: NONE > >
Hi Just a note on the history of these jaxws based modules. We had the Axis2 based ws binding in the 1.x code based and we ported this over to the 2.x code base. This is our primary binding for web services support and binding-ws-runtime-axis2 is the 2.x binding that is spec compliant and passes the OASIS tests. After we'd ported the axis binding to 2.x we started looking at whether we could simplify and, as the JVM supports JAXWS, we reasoned that we could build the binding based on just the standard JAXWS API. As a proof point we built binding-ws-runtime-jaxws which provides the general runtime and binding-ws-runtime-jaxws-ri which uses the JAXWS reference implementation provided by the JVM for the web services support. In theory, as Axis2 is a JAXWS provider we could have binding-ws-runtime-jaxws-axis2 but we didn't get that far. So the binding-ws-runtime-jaxws-ri runtime works in the sense that you can send and receive message but it's not SCA WS spec compliant. We could maybe stop releasing these modules if they are causing confusion Simon. -- Apache Tuscany committer: tuscany.apache.org Co-author of a book about Tuscany and SCA: tuscanyinaction.com
