RE: [wsrp-webservice] FYI .NET <--> JAX-RPC interop

That would be great! It's our 1.0 TC Spec wsdl (on the Oasis TC 
page: http://www.oasis-open.org/committees/wsrp/specifications/version1/wsrp_service.wsdl)

 

For 
our initCookie operation (which returns no result) this generates  (hope my 
cuts&pastes are correct):

 

// 
<remarks/>
  [System.Web.Services.WebMethodAttribute(EnableSession=true)]
  [System.Web.Services.Protocols.SoapDocumentMethodAttribute("urn:oasis:names:tc:wsrp:v1:initCookie", 
Use=System.Web.Services.Description.SoapBindingUse.Literal, 
ParameterStyle=System.Web.Services.Protocols.SoapParameterStyle.Bare)]
  [return: 
System.Xml.Serialization.XmlArrayAttribute("initCookieResponse", 
Namespace="urn:oasis:names:tc:wsrp:v1:types")]
  [return: 
System.Xml.Serialization.XmlArrayItemAttribute("extensions", 
Namespace="urn:oasis:names:tc:wsrp:v1:types", 
IsNullable=false)]
  public System.Xml.XmlElement[] 
initCookie([System.Xml.Serialization.XmlElementAttribute("initCookie", 
Namespace="urn:oasis:names:tc:wsrp:v1:types")] initCookie 
initCookie1)

  {
  }

 

----------------------------------------------

On the wire this (unless one builds XML result by hand) 
this results in an empty soap body:

 

<?xml version="1.0" encoding="utf-8" ?> 
- <soap:Envelope 
xmlns:soap="http://schemas.xmlsoap.org/soap/envelope/" 
xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" 
xmlns:xsd="http://www.w3.org/2001/XMLSchema">
- 
<soap:Header>
- <wsu:Timestamp xmlns:wsu="http://schemas.xmlsoap.org/ws/2002/07/utility">
  
<wsu:Created>2003-06-24T16:41:10Z</wsu:Created> 
  
<wsu:Expires>2003-06-24T16:46:10Z</wsu:Expires> 
  
</wsu:Timestamp>
  </soap:Header>
  <soap:Body 
/> 
  </soap:Envelope>

 

-----------------------------------------------

 

It 
would be great if .NET generated:

 

// 
<remarks/>
  [System.Web.Services.WebMethodAttribute(EnableSession=true)]
  [System.Web.Services.Protocols.SoapDocumentMethodAttribute("urn:oasis:names:tc:wsrp:v1:initCookie", 
Use=System.Web.Services.Description.SoapBindingUse.Literal, 
ParameterStyle=System.Web.Services.Protocols.SoapParameterStyle.Bare)]
  [return: 
System.Xml.Serialization.XmlElementAttribute("initCookieResponse", 
Namespace="urn:oasis:names:tc:wsrp:v1:types")]

  public InitCookieResponse 
initCookie([System.Xml.Serialization.XmlElementAttribute("initCookie", 
Namespace="urn:oasis:names:tc:wsrp:v1:types")] initCookie 
initCookie1)
  {
  }

 

and an 
InitCookieResponse class:

 

[System.Xml.Serialization.XmlTypeAttribute(Namespace="urn:oasis:names:tc:wsrp:v1:types")]
 public 
class InitCookieResponse
 {
 }

 

--------------------------------------

 

then we would get 
the "InitCookieResponse" body that JAX-RPC expects:

 

<?xml version="1.0" encoding="utf-8" ?> 

- 
<soap:Envelope xmlns:soap="http://schemas.xmlsoap.org/soap/envelope/" 
xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" 
xmlns:xsd="http://www.w3.org/2001/XMLSchema"> 

- 
<soap:Header> 

- 
<wsu:Timestamp xmlns:wsu="http://schemas.xmlsoap.org/ws/2002/07/utility"> 

<wsu:Created>2003-06-27T09:48:41Z</wsu:Created> 

<wsu:Expires>2003-06-27T09:53:41Z</wsu:Expires> 

</wsu:Timestamp> 

</soap:Header> 

- 
<soap:Body> 

<initCookieResponse 
xmlns="urn:oasis:names:tc:wsrp:v1:types" /> 

</soap:Body> 

</soap:Envelope>

I've 
not checked that this is a know interop issue or whether WS-I.org says empty 
SOAP bodies are ok for void operations.

 

regards,

Andre

 

 -----Original 
Message-----
From: David Holladay 
[mailto:]
Sent: 27 June 2003 
00:52
To: Andre Kramer; 

Cc: 

Subject: RE: [wsrp-webservice] FYI 
.NET <--> JAX-RPC interop

  

  
If you can pass along 
  the service's WSDL and the message you expect to get back (the one that makes 
  JAX-RPC happy), I'll have our VS.Net 2003 guys take a look at it as 
  well...

  
 

  

  

  
  

  
From: Andre 
  Kramer [mailto:] 
Sent: Wednesday, June 25, 2003 6:05 AM
To: 
  ''
Cc: 
  
Subject: [wsrp-webservice] FYI .NET 
  <--> JAX-RPC interop

  
 

  
.NET (Visual Studio 2003 Web 
  Services) generates and empty SOAP body (i.e. no Response sub-element) for our 
  void operations. We suspect that this may be causing JAX-RPC RI problems handling initCookie() replies 
  from .NET. David Ward spotted this omission and I'm going to check if adding a 
  response body by hand helps.

  
regards, 
Andre