wcf-interoperability | 易学教程

WCF: Is using WsHttpBinding interoperable?

阅读更多关于 WCF: Is using WsHttpBinding interoperable?

问题 As the name states... right now I'm using BasicHttpBinding, but I'm wondering if I can switch to WSHttpBinding and still be interoperable with, for example, Java. 回答1: wsHttpBinding and the newer ws2007HttpBinding both implement WS-* standards. You may have to configure the details so that they interoperate with your specific clients. 回答2: WSHttpBinding offers a lot of interoperable features but in the same time it by default uses message security with Windows authentication, service

Java Web Service Client to WCF Web Service Server. Interoperability Solution

阅读更多关于 Java Web Service Client to WCF Web Service Server. Interoperability Solution

问题 Has anyone found a way for a WCF Service to be queried by a Java Client? What .NET library did you use and what Java library did you use. Please be specific with specific platforms and library versions. Also, I've found that if the libraries don't use compatible SOAP version specifications that the libraries aren't compatible either. If you know which SOAP version specification, please provide that as well. -Thanks 回答1: What problems you for-see if you go ahead with calling your WCF service

WCF/WebService: Interoperable exception handling

阅读更多关于 WCF/WebService: Interoperable exception handling

问题 I understand that WCF will convert an exception into a fault and send it back as a SOAP message, but I was wondering if this is truly interoperable. I guess I'm having a tough time trying to figure out this possible scenario: Client (Java) calls a WCF Service (LoginService). Server checks for proper authorization, user authorization fails. Server throws an UnauthorizedAccessException. WCF converts this into a Fault somehow. (* - See Below As Well) Client has to be able to know how to read

What should I know when developing interoperable WCF web service?

阅读更多关于 What should I know when developing interoperable WCF web service?

问题 I'm starting this Wiki to collect best practices about creating interoperable web services (not clients) in WCF. Please share your experience if you know any feature which is not generally interoperable or which is not interoperable with specific platform. 回答1: Fairly simple: avoid any .NET specifics like Exceptions (turn them into SOAP faults) don't use any binding that start with net like netTcp, netNamedPipes, netMsmq and so forth - use wsHttpBinding for secure WS-* services, and

WCF/WebService: Interoperable exception handling

阅读更多关于 WCF/WebService: Interoperable exception handling

I understand that WCF will convert an exception into a fault and send it back as a SOAP message, but I was wondering if this is truly interoperable. I guess I'm having a tough time trying to figure out this possible scenario: Client (Java) calls a WCF Service (LoginService). Server checks for proper authorization, user authorization fails. Server throws an UnauthorizedAccessException. WCF converts this into a Fault somehow. (* - See Below As Well) Client has to be able to know how to read this Fault. I guess I'm just having a tough time understanding how this could still be interoperable

Getting WCF to accept unsigned 'To' Header

阅读更多关于 Getting WCF to accept unsigned 'To' Header

问题 I have a WCF web service that is using WSHttpBinding. The security is TransportWithMessageCredential. I have a client connecting to me that is sending a Soap message with the To element in the header unsigned. My service doesn't like this and is throwing System.ServiceModel.Security.MessageSecurityException with the message "The message received over Transport security has unsigned 'To' header". I haven't been able to find the signing of the element specified specifically in the WS-Security

WCF: Is using WsHttpBinding interoperable?

阅读更多关于 WCF: Is using WsHttpBinding interoperable?

As the name states... right now I'm using BasicHttpBinding, but I'm wondering if I can switch to WSHttpBinding and still be interoperable with, for example, Java. wsHttpBinding and the newer ws2007HttpBinding both implement WS-* standards. You may have to configure the details so that they interoperate with your specific clients. WSHttpBinding offers a lot of interoperable features but in the same time it by default uses message security with Windows authentication, service credentials negotiation over SPNego protocol and security context (WS-SecureConversation). Windows authentication and

What should I know when developing interoperable WCF web service?

阅读更多关于 What should I know when developing interoperable WCF web service?

I'm starting this Wiki to collect best practices about creating interoperable web services (not clients) in WCF. Please share your experience if you know any feature which is not generally interoperable or which is not interoperable with specific platform. Fairly simple: avoid any .NET specifics like Exceptions (turn them into SOAP faults) don't use any binding that start with net like netTcp, netNamedPipes, netMsmq and so forth - use wsHttpBinding for secure WS-* services, and basicHttpBinding for maximum reach / compatibility with even the weirdest client platforms don't use the