On Thu, Apr 30, 2009 at 12:51 PM, Raymond Feng wrote:
> More comments inline.
> For example, we have a java method A talking to B:
>
> A:
> void updateAddress(String customerId, AddressSDO address)
>
> B:
> @RequestWrapper(...)
> @ResponseWrapper(...)
> void updateAddress(String customerId, A
More comments inline.
--
From: "Scott Kurz"
Sent: Thursday, April 30, 2009 9:12 AM
To:
Subject: Re: why do we use JAXB declaredType unmarshalling instead of global
element unmarshalling?
Thanks. Replied...
On Thu, Apr 30, 2009 a
Thanks. Replied...
On Thu, Apr 30, 2009 at 11:43 AM, Raymond Feng wrote:
> 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
o use JAXB unmarshalling without a declared type?
Thanks,
Raymond
--
From: "Scott Kurz"
Sent: Thursday, April 30, 2009 7:39 AM
To:
Subject: why do we use JAXB declaredType unmarshalling instead of global
element unmarshalling?
I was askin
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
