Win a copy of The Little Book of Impediments (e-book only) this week in the Agile and Other Processes forum!
  • Post Reply
  • Bookmark Topic Watch Topic
  • New Topic

SOAP 1.2 RPC return values

 
Sim Kim
Ranch Hand
Posts: 268
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
As per the

As per http://www.idealliance.org/papers/xmle02/dx_xmle02/papers/02-02-02/02-02-02.html#ex6

SOAP 1.2 also adds a new convention for representing RPC return values



Using Glassfish for SOAP 1.2 RPC type didn't gave me such repsone.The response element was not named "rpc:result"
 
Peer Reynders
Bartender
Posts: 2968
6
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
Consider namespaces!

As long it resolves to

Glassfish is fine.

4.2.2 RPC Response
Ronald Bourret's XML Namespaces FAQ
James Clark: XML Namespaces

Furthermore
As mentioned in section 2. SOAP Data Model, use and implementation of the SOAP RPC Representation is OPTIONAL.



The purpose of the SOAP Data Model is to provide a mapping of non-XML based data to some wire representation. It is important to note that use of the SOAP Data Model, the accompanying SOAP Encoding (see 3. SOAP Encoding), and/or the SOAP RPC Representation (see 4. SOAP RPC Representation) is OPTIONAL. Applications which already model data in XML may not need to use the SOAP Data Model. Due to their optional nature, it is NOT a requirement to implement the SOAP Data Model, the SOAP Encoding and/or the SOAP RPC Representation as part of a SOAP node.


So Java EE 5 may not even support it. I'm pretty sure that they had no intention of supporting RPC/encoded (only RPC/literal) after all the problems that it caused, so there may be no need to support this.
 
Sim Kim
Ranch Hand
Posts: 268
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
Peer,

I didn't get you. the response which I got from Glassfish didn't had any word called "result" , forget namespace !

So what do you say ? I am asking with respect to SCDJWS5 . What should one understand ? The response to RPC request by a JEE server would be have "result" or not .

Sorry I am being too naive !
 
Peer Reynders
Bartender
Posts: 2968
6
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
JAX-WS 2.1 specification

3.6.2.3 RPC
This style is identified by a javax.jws.SOAPBinding annotation with the following properties: a style
of RPC, a use of LITERAL and a parameterStyle of WRAPPED.


  • JAX-WS only supports the LITERAL mode for RPC.
  • In LITERAL mode the WSDL governs the data layout - not SOAP.
  • Support for the SOAP Data Model, SOAP Encoding, SOAP RPC Representation is optional under SOAP 1.2.


  • So it looks to me that Java EE 5 doesn't support the SOAP 1.2 SOAP Data Model, SOAP Encoding, and SOAP RPC Representation (as it is optional and unnecessary) - which means it should be irrelevant to the SCDJWS5.

    Which style of WSDL should I use?
    [ November 13, 2008: Message edited by: Peer Reynders ]
     
    • Post Reply
    • Bookmark Topic Watch Topic
    • New Topic