There are a few thoughts behind:
1) In SCA, JAXB objects are not always used for doc-lit wrapper style Web
Service. There are cases that the transformer convert XML data into a JAXB
object without a global element. For example, the XSD only contains type
definitions.
2) We also deal with data transformation from non-wrapper to wrapper JAXB
which child elements from the source operation are converted to child
objects under the JAXB wrapper.
3) We treat POJOs as JAXB objects. I cannot remember if the global-element
based unmarshalling works for them.
What's the benefit to use JAXB unmarshalling without a declared type?
Thanks,
Raymond
--------------------------------------------------
From: "Scott Kurz" <[email protected]>
Sent: Thursday, April 30, 2009 7:39 AM
To: <[email protected]>
Subject: why do we use JAXB declaredType unmarshalling instead of global
element unmarshalling?
I was asking this question wrt, e.g. OMElement2JAXB.
If we have WS-I compliant WSDL then we always have a global element.
Is it because we're counting on this code to, say, deserialize
component property values expressed in SCDL documents?
Was planning on suggesting global elem unmarshalling as an improvement
but first thought it was worth understanding why we do this today.
Thanks,
Scott
