Hi Mark,
I do not know of any issues, nor i have i used .Net 3.5 as a client. I
would expect that the HTTP interop should work fine, as that layer has
been established for a long time.
For XML interop of representations, when data-binding is used, i think
it is a matter of using interoperable schema on both sides that
produces consumable XML (it does not have be be tightly bound to one
exact schema as may be the case for schema embedded in WSDL).
Paul.
On Mar 6, 2009, at 6:16 PM, Rabick, Mark A (MS) wrote:
> It looks one of our webservice customers will be implementing their
> clients using .NET 3.5 and C#. I've been looking around the wiki
> and mailing lists to see if there are any issues regarding XML
> interoperability and Jersey/JAXB.
>
> The Sun JAX-WS reference implementation included in Metro web
> services stack (https://jax-ws.dev.java.net/) includes the WSIT (Web
> Services Interoperabilty Toolkit) extension. It's supposed to
> support interop with the Windows Communication Framework (WCF)
> in .NET 3.0/3.5.
>
> Are there similar/different issues for .NET 3.5 clients and Jersey?
>
> JAX-RS avoids a lot of the interop issues by avoiding the WS-*
> standards. Has anyone used .NET 3.5 to integrate with Jersey (JAX-
> RS) web services?
>
> Thanks,
>
> -mark
>
> _______________________________________________
> Mark A. Rabick
> Software Engineer
> Northrop Grumman - Integrated Mission Systems (IS/DSD/IMS)
> Em: mark.rabick_at_ngc.com
>