When all the stars start to get aligned...

Discovered a cool post on WCF position regarding RPC-literal: "RPC" vs. Messaging in WCF.
It looks like the old position, from the early days of .NET is no longer the norm. The choice is back to the developers. Now, we can rename this post the way it was supposed to be name: 'RPC/Literal and French Choice'.

The way to go forward is still with the Document-Literal-MSS [Microsoft Secret Sauce] format, a.k.a Wrapped style. The legacy is sutch that you will have interoperability problem if you use this message format with a non-indigo based .NET framework.

-ecco

Comments

Post a Comment

Popular posts from this blog

Changing the version of JDK used by JDeveloper

I have recently learned a quick and lazy way to change the version of the JDK used to run JDeveloper 10g R3. I am sure there is an option somewhere in the configuration screen to do the same, which I couldn't find... While JDeveloper is not running, locate the embedded JDK on disk and rename (or delete) that directory. For me, it was C:\opt\jdev\jdk. Once it's done, restart and you will by asked to locate the version of the JDK you want to use. It's another step to get going with JAVA on Vista. -ecco
Read more

Connection reset from a WCF Web Service

Here is an error message you may see, when calling WCF Web Services from java: IOException retrieving the response: java.net.SocketException: Connection reset As it may not be obvious the first time you see it, this may save you some time. One reason for this behaviour is when the WCF endpint is expecting to see wsa:Action SOAP header in the request. To find out if you are facing this case, you have to look inside the WSDL, and search for the policy that describes the contract for your endpoint. <wsp:Policy wsu:Id="CustomBinding_Echo1_policy">   <wsp:ExactlyOne>     <wsp:All>       <wsaw:UsingAddressing/>     </wsp:All>   </wsp:ExactlyOne> </wsp:Policy> To make this a concrete example, here is a sample WSDL . To find the policy, you will need to follow the import as the policy are not always advertized in the top-level document. Here is how the import looks:   <wsdl:import namespace="http://example.org/" location="h
Read more

unexpected null value for literal data

There is a challenge that is hard to overcome at first; making sense of error messages. You can always Google with the text of the error, “unexpected null value for literal data” and hope to be lucky . If you are using Oracle Application Server 10.1.3.0, here is the explaination for the message and two ways out. The Exception: unexpected null value for literal data at oracle.j2ee.ws.common.util.exception.JAXRPCExceptionBase.<init>(JAXRPCExceptionBase.java:52) at oracle.j2ee.ws.common.encoding.SerializationException.<init>(SerializationException.java:26) ... The relevant schema: <complexType name="Customer"> <sequence> <element name="address" type="tns:Address"/> <element name="firstName" type="string"/> <element name="lastName" type="string"/> </sequence> </complexType> A sample code that will cause this exception: public void testServ() throw
Read more