JBossWS / JAXB integration -------------------------- A SOAP envelope targeted to JBossWS or emitted from JBossWS can either be of RPC or DOCUMENT style. The encoding is always literal.
DOCUMENT style -------------- | <soap:Envelope> | <soap:Header> + | <header-element> * | </soap:Header> | <soap:Body> | <single-document-element> | </soap:Body> | </soap:Envelope> | The body contains a single complex element, which is completely defined in XML schema. The optional header elements may be simple or complex types. In case of a complex type, it must be defined in schema. Here is an example | <soap:Envelope> | <soap:Header> | <tns:SimpleHeader>123456</tns:SimpleHeader> | <tns:ComplexHeader> | <name>Tom</name> | <age>3</age> | </tns:ComplexHeader> | </soap:Header> | <soap:Body> | <tns:PurchaseOrder> | <item>Ferrari</item> | <address> | <street>Wall Street 102</street> | <city>New York</city> | </address> | </tns:PurchaseOrder> | </soap:Body> | </soap:Envelope> | The corresponding schema may look as follows | <schema> | <complexType name="ComplexHeaderType"> | <sequence> | <element name="name" type="xsd:string"/> | <element name="age" type="xsd:int"/> | </sequence> | </complexType> | <element name="ComplexHeader" type="tns:ComplexHeaderType"> | | <complexType name="PurchaseOrderType"> | <sequence> | <element name="item" type="xsd:string"/> | <element name="address"> | <complexType> | <sequence> | <element name="street" type="xsd:string"/> | <element name="city" type="xsd:string"/> | </sequence> | </complexType> | </element> | </sequence> | </complexType> | <element name="PurchaseOrder" type="tns:PurchaseOrderType"> | <schema> | Note, the schema does not contain a definition for <tns:SimpleHeader/> which would be defined in the WSDL. The JAXB marshalling layer can only unmarshall the xml fragments that are defined in schema. The other fragments must be handled in the JBossWS layer, which is WSDL aware. RPC style --------- | <soap:Envelope> | <soap:Header> + | <header-element> * | </soap:Header> | <soap:Body> | <rpc-wrapper-element> | <rpc-parameter> * | </rpc-wrapper-element> | </soap:Body> | </soap:Envelope> | The body contains a RPC wrapper element, which indentifies the RPC operation. Optional child elements of the rpc-wrapper-element may be simple or complex types. In case of a complex type, it must be defined in schema. The optional header elements may be simple or complex types. In case of a complex type, it must be defined in schema. Here is an example | <soap:Envelope> | <soap:Header> | <tns:SimpleHeader>123456</tns:SimpleHeader> | <tns:ComplexHeader> | <name>Tom</name> | <age>3</age> | </tns:ComplexHeader> | </soap:Header> | <soap:Body> | <tns:PurchaseOrder> | <tns:item>Ferrari</tns:item> | <tns:address> | <street>Wall Street 102</street> | <city>New York</city> | </tns:address> | </tns:PurchaseOrder> | </soap:Body> | </soap:Envelope> | The corresponding schema may look as follows | <schema> | <complexType name="ComplexHeaderType"> | <sequence> | <element name="name" type="xsd:string"/> | <element name="age" type="xsd:int"/> | </sequence> | </complexType> | <element name="ComplexHeader" type="tns:ComplexHeaderType"> | | <complexType name="AddressType"> | <sequence> | <element name="street" type="xsd:string"/> | <element name="city" type="xsd:string"/> | </sequence> | </complexType> | <element name="address" type="tns:AddressType"> | <schema> | Note, the schema does not contain a definition for <tns:SimpleHeader/> nor <tns:PurchaseOrder/> nor <tns:item> These would be defined in the WSDL. The JAXB marshalling layer can only unmarshall the xml fragments that are defined in schema. The other fragments must be handled in the JBossWS layer, which is WSDL aware. SOAPContentElement ------------------ The SAAJ API offers a DOM based object view of the SOAP envelope. For this dicussion we look at the following interfaces SOAPEnvelope, SOAPHeader, SOAPHeaderElement, SOAPBody, SOAPBodyElement. They all extend SOAPElement, which implements org.w3c.dom.Element. When unmarshalling a SOAP message, JBossWS first chops the message into fragments. Here the XML fragments resulting from the DOCUMENT message. | <tns:SimpleHeader>123456</tns:SimpleHeader> | | | <tns:ComplexHeader> | <name>Tom</name> | <age>3</age> | </tns:ComplexHeader> | | | <tns:PurchaseOrder> | <item>Ferrari</item> | <address> | <street>Wall Street 102</street> | <city>New York</city> | </address> | </tns:PurchaseOrder> | and here the XML fragments resulting from the RPC message. | <tns:SimpleHeader>123456</tns:SimpleHeader> | | | <tns:ComplexHeader> | <name>Tom</name> | <age>3</age> | </tns:ComplexHeader> | | | <tns:item>Ferrari</tns:item> | | | <tns:address> | <street>Wall Street 102</street> | <city>New York</city> | </tns:address> | | XML framents can be marshalled into Java objects and vice versa. The SAAJ object tree (it is not a graph) is constructed with object instances of the above interfaces. The XML fragments are assigened to JBossWS specific instances of SOAPContentElement. There are no deep elements created for the content of the XML fragments. http://cvs.sourceforge.net/viewcvs.py/jboss/webservice/src/main/org/jboss/ws/soap/SOAPContentElement.java?view=markup | /** | * A SOAPElement that gives access to its content as XML fragment or Java object. | * | * The SOAPContentElement has three content representations, which may exist in parallel. | * The getter and setter of the content properties perform the conversions. | * It is the responsibility of this objects to keep the representations in sync. | * | * +---------+ +-------------+ +-------------+ | * | Object | <-----> | XMLFragment | <-----> | DOMTree | | * +---------+ +-------------+ +-------------+ | * | * The idea is, that jaxrpc handlers can work with both the object and the DOM view of this SOAPElement. | * Note, that state transitions may be expensive. | * | * @author [EMAIL PROTECTED] | * @since 13-Dec-2004 | */ | After the SOAPContentElemets have been constructed, they are not yet associated with an xmlType nor its corresponding Java type. In a previous design it was the responsiblity of the BindingProvider to perform marshalling/unmarshalling of the entire SOAPMessage. This has now changed such that the SOAPContentElement performs marshalling/unmarshalling of its xmlFragment into a Java object and vice versa on demand. JAXRPC compliant handlers access the SAAJ or DOM API of the SOAPContentElement, walking trees and accessing text content. JBossWS however provides the handlers access to the assocciated Java object, which is much more intuitive. This functionality may become part of JAXRPC-2.0. JBossWS Serializer/Deserializer ------------------------------- JBossWS defines the following signature in Serializer/Deserializer implementations | String serialize(QName xmlName, QName xmlType, Object value, SerializationContextImpl serContext); | | Object deserialize(QName xmlName, QName xmlType, String xmlFragment, SerializationContextImpl serContext); | The SerializationContext gives access to these properties | // The type mapping that is valid for this serialization context | private LiteralTypeMapping typeMapping; | | // The namespace registry that is valid for this serialization context | private NamespaceRegistry namespaceRegistry; | | // A registry of xmlType to schema location URL | private SchemaLocationRegistry xsdRegistry; | There are number of simple type Serializer/Deserializers defined in package http://cvs.sourceforge.net/viewcvs.py/jboss/webservice/src/main/org/jboss/ws/jaxrpc/encoding which deal with the standard XSD schema types. All other types will be handled by JAXBSerializer/JAXBDeserializer JBossWS / JAXB contract ----------------------- JAXB will be used to marshall/unmarshall XML fragments that are defined by complex schema types into Java objects and vice versa. JBossWS provides: 1) The xmlName of the root element, as QName 2) The xmlType of the complex schema type, as QName 3) The xmlFragment for unmarshalling 4) The Java object for marshalling 5) The URL to the schema that contains an element definition for xmlName 6) A registry of previously definied prefix <-> namespaceURI mappings JAXB will not be required to do schema less marshalling/unmarshalling. Instead, if there is no user defined schema, JBossWS uses its internal tools for on-the-fly schema generation of complex types. Since JAXB will marshall/unmarshall simple types as well, it is important that the JBossWS Serializer/Deserializer and JAXB share the same codebase for that functionality. In case JAXB provides schema less marshalling/unmarshallin, it should share the code base for on-the-fly schema generation. Standalone JAXB marshalling/unmarshalling should not yield to different results than going through the JBossWS layer for the same functionality. Thanks for reading this! Feedback is of course welcome. View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=3858599#3858599 Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=3858599 ------------------------------------------------------- SF email is sponsored by - The IT Product Guide Read honest & candid reviews on hundreds of IT Products from real users. Discover which products truly live up to the hype. Start reading now. http://productguide.itmanagersjournal.com/ _______________________________________________ JBoss-Development mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/jboss-development
