[
https://issues.apache.org/jira/browse/TUSCANY-2084?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Scott Kurz updated TUSCANY-2084:
--------------------------------
Component/s: Java SDO Implementation
Java SCA Data Binding Runtime
Fix Version/s: Java-SCA-Next
Affects Version/s: Java-SCA-1.1
> Problems deserializing XML->SDO after using XMLType element calculated from
> Java to serialize SDO->XML onto
> ------------------------------------------------------------------------------------------------------------
>
> Key: TUSCANY-2084
> URL: https://issues.apache.org/jira/browse/TUSCANY-2084
> Project: Tuscany
> Issue Type: Bug
> Components: Java SCA Data Binding Runtime, Java SDO Implementation
> Affects Versions: Java-SCA-1.1
> Reporter: Scott Kurz
> Fix For: Java-SCA-Next
>
>
> Discussed in this thread:
> http://www.mail-archive.com/[email protected]/msg28304.html
> Personally I worked around this by changing SDODatabinding.introspect() to do:
> dataType.setLogical(new XMLType(null, xmlType));
> //dataType.setLogical(new XMLType(elementName, xmlType));
> But Raymond suggested possibly fixing this in the SDO impl. It would also
> be possible to leave introspection the same
> but workaround this in the SDO transformers.
> Note that if you use the WS binding you typically won't see this, because the
> presence of the WSDL intf on the XML side of things
> gives you a real element to serialize into, one that SDO can recognize during
> deserialization. You have to have a binding without a WSDL intf
> that you're transforming across.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
