• Post Reply Bookmark Topic Watch Topic
  • New Topic
programming forums Java Mobile Certification Databases Caching Books Engineering Micro Controllers OS Languages Paradigms IDEs Build Tools Frameworks Application Servers Open Source This Site Careers Other Pie Elite all forums
this forum made possible by our volunteer staff, including ...
Marshals:
  • Campbell Ritchie
  • Ron McLeod
  • Paul Clapham
  • Tim Cooke
  • Devaka Cooray
Sheriffs:
  • Liutauras Vilda
  • paul wheaton
  • Rob Spoor
Saloon Keepers:
  • Tim Moores
  • Stephan van Hulst
  • Tim Holloway
  • Piet Souris
  • Mikalai Zaikin
Bartenders:
  • Carey Brown
  • Roland Mueller

How rpc literal non standard types are mapped in JAVAt?

 
Greenhorn
Posts: 9
  • Mark post as helpful
  • send pies
    Number of slices to send:
    Optional 'thank-you' note:
  • Quote
  • Report post to moderator
Hi.. I'm reading RMH. In Mappings fom Java to XML and WSDL topic he mentioned about how a document literal non standard type is mapped to JAVA (Using SOAPElement)..

My doubt is how RPC literal non standard types are mapped to JAVA?
 
Bartender
Posts: 2968
6
  • Mark post as helpful
  • send pies
    Number of slices to send:
    Optional 'thank-you' note:
  • Quote
  • Report post to moderator
JSR-101 Java� API for XML-based RPC JAX-RPC 1.1


6.4.1 Java Mapping of Literal Representation
...
If there is no standard Java mapping for an XML schema type, a message part with
literal representation is considered and mapped as a document fragment. The XML to
Java mapping uses the interface "javax.xml.soap.SOAPElement" to represent a literal
message part in the Java mapping of a "wsdl:operation" element. For example, a
parameter or a return type (for a remote operation) represented as a literal message part
is mapped to a "SOAPElement" in the Java method signature.



This pertains to any literal representation, i.e. document/literal and rpc/literal. The only difference is that for document/literal the entire document (which is the one single part in the WSDL message) is a SOAPElement; for RPC/Literal a parameter (one of the possibly many parts for that WSDL message) becomes a SOAPElement.

The previous paragraph in the specification is restricted to "document" because it is talking about the "wrapped" style.
[ May 13, 2008: Message edited by: Peer Reynders ]
 
it's a teeny, tiny, wafer thin ad:
We need your help - Coderanch server fundraiser
https://coderanch.com/wiki/782867/Coderanch-server-fundraiser
reply
    Bookmark Topic Watch Topic
  • New Topic