RE: WSDL interop question using .NET service and Axis2 0.94 client

DeRemer, Bob Tue, 28 Mar 2006 07:10:22 -0800

Title: WSDL interop question using .NET service and Axis2 0.94 client

Florian,

Off hand, I'm not sure what is causing your problem - I haven't run into this myself yet. That said, I'm assuming you are using .NET 2.0 + WSE 3 on the client. IF so, make sure you have configured you WSE Messaging settings for to set the "Client Mode" to On. I apologize if this is a basic question, but I find it's better to check the simpler things first. If that doesn't turn up anything, then turn on the diagnostic tracing in your WSE settings for both incoming and outgoing messages, and set it to send detailed error information.

Hope this helps. Regards,

Bob

From: Florian Rengers [mailto:[EMAIL PROTECTED]
Sent: Tuesday, March 28, 2006 9:46 AM
To: [email protected]
Cc: DeRemer, Bob
Subject: Re: WSDL interop question using .NET service and Axis2 0.94 client

Hi Bob,

I have a Interop-problem.
I wrote a Service based on the Java-Technology JAX-WS which provides documents MTOM encoded and I wrote a consumer-client in c#.NET.

On client-side I get an exception during deserialisation the response-message:

System.InvalidOperationException
Client found response content type of
'Multipart/Related; type=\"application/xop+xml\"; boundary=\"----=_Part_0_24598445.1143476873406\"; start-info=\"text/xml\"',
but expected 'text/xml'.

I sniffed the in- and outcomming messages. Here is the JAX-WS response(shorted):

***************************************************************************
  Server: Apache-Coyote/1.1
  Set-Cookie: JSESSIONID=6156A549140745D2AD142A1F826387A4; Path=/geoengine
  Content-Type: Multipart/Related; type="application/xop+xml"; boundary="----=_Part_2_18504142.1143467055109"; start-info="text/xml"
  Content-Length: 59571
  Date: Mon, 27 Mar 2006 13:44:15 GMT
 
  ------=_Part_2_18504142.1143467055109
  Content-Type: application/xop+xml; type="text/xml"; charset=utf-8
 
  <soap:Envelope>
  ...
  ...
  </soap:Envelope>
  ------=_Part_2_18504142.1143467055109
  Content-Type: application/octet-stream
  Content-ID: <[EMAIL PROTECTED]>
  Content-transfer-encoding: binary
 
  [BINARY DATA]
 
  ------=_Part_2_18504142.1143467055109--
***************************************************************************

The only significant difference between .NET request and JAX-WS response I found is that the .NET request has an additional property "start" in its content-header which links to the message-part and "charset" is set to "utf-8".

Could this be the reason for the fault?

Best Regards

Florian
DeRemer, Bob schrieb:

I'm a software architect who has been working with distributed MS technologies since 97. I have been working with ASMX 2.0 and WSE3, along with the Indigo beta bits for a while. I am now starting to dive deep into both Axis2 and the Sun JWSDP 2 implementations to see where the gaps are and just how well the frameworks interoperate when using more advanced WS technologies (i.e. TCP hosting, MTOM, custom transports, etc.).

As such, I'm focusing on the contract-first approach - creating my WSDL, then generating my respective .NET and Java implementations.

I've come across a couple issues when running WSDL2Java on doc/literal WSDL - one of which has already been reported on this list. The other may be WSDL2Java user error, but I'm not sure.

Question #1 [already reported against 0.94]:
WSDL2Java throws an exception when the the WSDL types section contains more than one restricted enumeration. This one has already been reported and apparently used to work in 0.93. So, hopefully, this will be an easy fix for a 0.94 patch or 0.95.

Question #2:
When I generate client proxy code for a message with a single <part name="parameters" …/> and document/literal binding and operations (i.e. NO rpc anywhere) I still end up with ADDBean-derived databound Java wrapper objects.

Is there a way to get the client proxy code to simply have a method with the actual parameters instead of the single databound wrapper object parameter? If I generate .NET client proxies, the code is the CLR types as generated from the XSD to CLR conversion - without any wrapper parameter object. Also, if I run the wscompile tool with the JWSDP 2, it generates the non-wrapped client proxy similar to .NET.

Thanks in advance for any help. Please let me know if you have any further questions!

Bob DeRemer
Sr. Software Architect

SAP Labs, LLC
350 Eagleview Blvd
Exton, PA 19341 USA
T1 +1.610.903.8000 x 136
T2 +1.717.505.7923
M +1.717.424.9595
E [EMAIL PROTECTED]

RE: WSDL interop question using .NET service and Axis2 0.94 client

Reply via email to