You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@tuscany.apache.org by "Simon Laws (JIRA)" <de...@tuscany.apache.org> on 2009/04/26 14:14:31 UTC

[jira] Resolved: (TUSCANY-2965) For JMS binding, add a jmsBytesXML wireFormat analogous to jmsTextXML

     [ https://issues.apache.org/jira/browse/TUSCANY-2965?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Simon Laws resolved TUSCANY-2965.
---------------------------------

       Resolution: Fixed
    Fix Version/s: Java-SCA-Next

Added wire format and simple itest

> For JMS binding, add a jmsBytesXML wireFormat analogous to jmsTextXML
> ---------------------------------------------------------------------
>
>                 Key: TUSCANY-2965
>                 URL: https://issues.apache.org/jira/browse/TUSCANY-2965
>             Project: Tuscany
>          Issue Type: Improvement
>          Components: Java SCA JMS Binding Extension
>            Reporter: Scott Kurz
>            Assignee: Simon Laws
>            Priority: Minor
>             Fix For: Java-SCA-Next
>
>
> Like jmsTextXML, for this jmsBytesXML wireFormat we will not unwrap a single argument input like the default wireFormat behavior proscribed in the JMS binding spec.   
> Though it would be conceivable to implement both jmsTextXML and jmsBytesXML  as a "single" wireFormat with an attribute to distinguish btw. bytes vs. text, I guess let's start by treating them as two separate wire formats.

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.