don't convert blank element or attribute into one with the default value during
deserialization
-----------------------------------------------------------------------------------------------
Key: TUSCANY-3377
URL: https://issues.apache.org/jira/browse/TUSCANY-3377
Project: Tuscany
Issue Type: New Feature
Components: Java SCA Assembly Model
Affects Versions: Java-SCA-Next
Reporter: Sean Zhou
the current Tuscany models convert blank element or attribute into one with the
default value during deserialization. This causes issues in tools that use
Tuscany models to read and write composite files.
For example,
After going through deserialization and serialization of Tuscany models, the
following binding.jms element is changed from
<binding.jms>
<destination name="jms/SCA_JMSSAMPLE_Log_Request" type="queue"/>
<response>
<destination name="jms/SCA_JMSSAMPLE_Log_Response"/>
<connectionFactory name="jms/SCA_JMSSAMPLE_Log_Response_CF"/>
</response>
<tuscany:wireFormat.jmsObject/>
</binding.jms>
to
<binding.jms>
<destination name="jms/SCA_JMSSAMPLE_Log_Request" type="queue"/>
<response>
<destination create="ifnotexist"
name="jms/SCA_JMSSAMPLE_Log_Response" type="queue"/>
<connectionFactory create="ifnotexist"
name="jms/SCA_JMSSAMPLE_Log_Response_CF"/>
<tuscany:wireFormat.jmsObject wrapSingle="false"/>
</response>
<tuscany:wireFormat.jmsObject wrapSingle="false"/>
</binding.jms>
As you see above, the create attribute, the wrapSingle attribute, and the
wireFormat.jmsObject in the response element are added. They don't make any
functional harm on the composite but they are confusing to the user because the
user didn't have those attributes and elements in the original composite.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
