Details
-
Bug
-
Status: Closed
-
Major
-
Resolution: Fixed
-
Java-SCA-2.0
-
None
-
None
-
All OS
Description
If I start out with a component like this
<service name="InvokeServiceOasis">
<binding.jms>
<tuscany:wireFormat.jmsObject/>
<activationSpec create="never" jndiName="jms/Oasis_JMS_AS"/>
<response>
<destination create="never" jndiName="jms/Oasis_JMS_Response" type="queue"/>
<connectionFactory create="never" jndiName="jms/Oasis_JMS_CF"/>
</response>
</binding.jms>
</service>
after it goes through the composite build process, the resulting component looks like this:
<service name="InvokeServiceOasis">
<binding.jms>
<tuscany:wireFormat.jmsObject/>
<activationSpec create="never" jndiName="jms/Oasis_JMS_AS"/>
<response>
<destination create="never" jndiName="jms/Oasis_JMS_Response" type="queue"/>
<connectionFactory create="never" jndiName="jms/Oasis_JMS_CF"/>
<tuscany:wireFormat.jmsObject/>
</response>
</binding.jms>
</service>
I am not sure if there is a reason why we need to write <tuscany:wireFormat.jmsObject/> into the response element and if we do need to include it for some reason, it should be the first element under the response. This causes a validation failure currently.