http://blog.callistaenterprise.se/2010/01/07/another-perspective-on-jax-ws-portability/ Our consultants share their reflections on IT architecture. Tue, 15 Nov 2011 07:33:10 +0000 http://wordpress.org/?v=2.9.1 hourly 1 http://blog.callistaenterprise.se/2010/01/07/another-perspective-on-jax-ws-portability/comment-page-1/#comment-5 Johan Eltes Tue, 23 Feb 2010 20:33:40 +0000 http://wiki.callistaenterprise.se//display/CallistaCom/2009/03/29/Another+perspective+on+JAX-WS+portability#comment-5 Another problem with wsimport (compared to CXF wsdl2java) that recently hit me, is the fact that wsimport validates the wsdl with a none-standard version of the wsdl schema. There are a couple of WSDL schemas around - all with the same namespace. WS-I defines which of them that should be used. Although JAX WS RI claims WS-I compliance, they fail in this case. I've reported the defect in the tracker for wsimport: <a href="https://jax-ws.dev.java.net/issues/show_bug.cgi?id=819" rel="nofollow">https://jax-ws.dev.java.net/issues/show_bug.cgi?id=819</a> Another problem with wsimport (compared to CXF wsdl2java) that recently hit me, is the fact that wsimport validates the wsdl with a none-standard version of the wsdl schema. There are a couple of WSDL schemas around – all with the same namespace. WS-I defines which of them that should be used. Although JAX WS RI claims WS-I compliance, they fail in this case. I’ve reported the defect in the tracker for wsimport: https://jax-ws.dev.java.net/issues/show_bug.cgi?id=819

]]>