This week's book giveaways are in the Java EE and JavaScript forums.
We're giving away four copies each of The Java EE 7 Tutorial Volume 1 or Volume 2(winners choice) and jQuery UI in Action and have the authors on-line!
See this thread and this one for details.
The moose likes Web Services and the fly likes How rpc literal non standard types are mapped in JAVAt? Big Moose Saloon
  Search | Java FAQ | Recent Topics | Flagged Topics | Hot Topics | Zero Replies
Register / Login


Win a copy of The Java EE 7 Tutorial Volume 1 or Volume 2 this week in the Java EE forum
or jQuery UI in Action in the JavaScript forum!
JavaRanch » Java Forums » Java » Web Services
Bookmark "How rpc literal non standard types are mapped in JAVAt?" Watch "How rpc literal non standard types are mapped in JAVAt?" New topic
Author

How rpc literal non standard types are mapped in JAVAt?

vinodreddy kisanagaram
Greenhorn

Joined: Jan 08, 2008
Posts: 9
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?


***<br />K Vinod Reddy
Peer Reynders
Bartender

Joined: Aug 19, 2005
Posts: 2922
    
    5
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 ]
 
I agree. Here's the link: http://aspose.com/file-tools
 
subject: How rpc literal non standard types are mapped in JAVAt?