You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@tuscany.apache.org by "ant elder (JIRA)" <de...@tuscany.apache.org> on 2009/10/16 15:17:31 UTC
[jira] Updated: (TUSCANY-3297) JMS Binding schema doens't allow
custom wireFormats in JMS response element
[ https://issues.apache.org/jira/browse/TUSCANY-3297?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
ant elder updated TUSCANY-3297:
-------------------------------
Component/s: (was: OASIS Compliance - OASIS)
OASIS Compliance - TUSCANY
> JMS Binding schema doens't allow custom wireFormats in JMS response element
> ---------------------------------------------------------------------------
>
> Key: TUSCANY-3297
> URL: https://issues.apache.org/jira/browse/TUSCANY-3297
> Project: Tuscany
> Issue Type: Bug
> Components: OASIS Compliance - TUSCANY
> Reporter: ant elder
> Fix For: Java-SCA-2.0
>
>
> The 1.1 CD04 version of the JMS Binding schema doens't appear to allow custom wireFormats in JMS response element so the following binding fails schema validation:
> <binding.jms>
> <destination jndiName="HelloWorldService1"/>
> <response>
> <tuscany:wireFormat.jmsObject />
> </response>
> </binding.jms>
> I've raised the issue with the JMS binding spec and will add a work around to the Tuscany JMS binding xsd for now
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.