You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@tuscany.apache.org by "Scott Kurz (JIRA)" <tu...@ws.apache.org> on 2008/03/14 15:40:25 UTC
[jira] Created: (TUSCANY-2084) Problems deserializing XML->SDO
after using XMLType element calculated from Java to serialize SDO->XML
onto
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
Reporter: Scott Kurz
Discussed in this thread:
http://www.mail-archive.com/tuscany-dev@ws.apache.org/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: tuscany-dev-unsubscribe@ws.apache.org
For additional commands, e-mail: tuscany-dev-help@ws.apache.org
[jira] Issue Comment Edited: (TUSCANY-2084) Problems deserializing
XML->SDO after using XMLType element calculated from Java to serialize
SDO->XML onto
Posted by "Scott Kurz (JIRA)" <tu...@ws.apache.org>.
[ https://issues.apache.org/jira/browse/TUSCANY-2084?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12582302#action_12582302 ]
scottkurz edited comment on TUSCANY-2084 at 3/26/08 7:51 AM:
--------------------------------------------------------------
There's a similar issue for dynamic SDO. Instead of doing:
if (dataType.getLogical() == null) {
dataType.setLogical(XMLType.UNKNOWN);
}
which has no impact now that Java introspection is setting up a logical DT with a default elem in it
(therefore it's non-null), I think we should just do an unconditional:
dataType.setLogical(XMLType.UNKNOWN);
to overwrite and to therefore allow SDO serialization to work.
was (Author: scottkurz):
There's a similar issue for dynamic SDO. Instead of just:
> 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/tuscany-dev@ws.apache.org/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: tuscany-dev-unsubscribe@ws.apache.org
For additional commands, e-mail: tuscany-dev-help@ws.apache.org
[jira] Commented: (TUSCANY-2084) Problems deserializing XML->SDO
after using XMLType element calculated from Java to serialize SDO->XML
onto
Posted by "Scott Kurz (JIRA)" <tu...@ws.apache.org>.
[ https://issues.apache.org/jira/browse/TUSCANY-2084?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12582302#action_12582302 ]
Scott Kurz commented on TUSCANY-2084:
-------------------------------------
There's a similar issue for dynamic SDO. Instead of just:
> 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/tuscany-dev@ws.apache.org/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: tuscany-dev-unsubscribe@ws.apache.org
For additional commands, e-mail: tuscany-dev-help@ws.apache.org
[jira] Commented: (TUSCANY-2084) Problems deserializing XML->SDO
after using XMLType element calculated from Java to serialize SDO->XML
onto
Posted by "Raymond Feng (JIRA)" <tu...@ws.apache.org>.
[ https://issues.apache.org/jira/browse/TUSCANY-2084?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12595674#action_12595674 ]
Raymond Feng commented on TUSCANY-2084:
---------------------------------------
I tried the following XML with SDO 1.1 release and it seems to be working fine:
private static final String XML =
"<ns:return xmlns:ns=\"http://services.move.ec3\" xmlns:ax21=\"http://types.move.ec3/xsd\" " + "xmlns:_typens_=\"http://types.move.ec3/xsd\" xmlns:xsi=\"http://www.w3.org/2001/XMLSchema-instance\" xsi:type=\"_typens_:Comment\">"
+ "<ax21:body>c</ax21:body><ax21:caption>b</ax21:caption><ax21:entryId>1</ax21:entryId><ax21:owner>a1</ax21:owner><ax21:reference>a1</ax21:reference><ax21:tstamp>2008-04-16T16:22:07.812Z</ax21:tstamp></ns:return>";
I assume it has been fixed in SDO 1.1.
Thanks,
Raymond
> 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/tuscany-dev@ws.apache.org/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.
[jira] Updated: (TUSCANY-2084) Problems deserializing XML->SDO
after using XMLType element calculated from Java to serialize SDO->XML
onto
Posted by "Scott Kurz (JIRA)" <tu...@ws.apache.org>.
[ 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/tuscany-dev@ws.apache.org/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: tuscany-dev-unsubscribe@ws.apache.org
For additional commands, e-mail: tuscany-dev-help@ws.apache.org