http://www.udidahan.com/2007/06/25/web-services-no-magic-bullet-for-net-java-interop/ Enterprise Development Expert & SOA Specialist Wed, 08 Sep 2010 18:14:32 -0500 http://wordpress.org/?v=2.8.4 hourly 1 http://www.udidahan.com/2007/06/25/web-services-no-magic-bullet-for-net-java-interop/comment-page-1/#comment-2590 Arnon Rotem-Gal-Oz Tue, 26 Jun 2007 04:34:11 +0000 http://udidahan.weblogs.us/2007/06/25/web-services-no-magic-bullet-for-net-java-interop/#comment-2590 Did you take a look at Sun's Tango project (or whatever it is called today) http://java.sun.com/developer/technicalArticles/glassfish/ProjectTango/ Did you take a look at Sun’s Tango project (or whatever it is called today) http://java.sun.com/developer/technicalArticles/glassfish/ProjectTango/

]]> http://www.udidahan.com/2007/06/25/web-services-no-magic-bullet-for-net-java-interop/comment-page-1/#comment-2585 Jeremy D. Miller Tue, 26 Jun 2007 02:12:27 +0000 http://udidahan.weblogs.us/2007/06/25/web-services-no-magic-bullet-for-net-java-interop/#comment-2585 We're doing interop between a Java webservice and .Net client through web services. Even using a common XSD/WSDL file to codegen both sides we still see problems with interop when you put the two halves together. The two serialization engines are both quirky and flawed in different ways. What we've found is that the Java serialization engines are strict on XSD compliance where the .Net serialization is too permissive. We’re doing interop between a Java webservice and .Net client through web services. Even using a common XSD/WSDL file to codegen both sides we still see problems with interop when you put the two halves together. The two serialization engines are both quirky and flawed in different ways. What we’ve found is that the Java serialization engines are strict on XSD compliance where the .Net serialization is too permissive.

]]>