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)" <tu...@ws.apache.org> on 2007/10/05 18:02:50 UTC

[jira] Resolved: (TUSCANY-1834) JMS Binding does not conform to the specification when selecting the opeartion to invoke

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

Simon Laws resolved TUSCANY-1834.
---------------------------------

    Resolution: Fixed

Thank you Mark. Just applied the patches.

As you will see the JMS binding is very incomplete so any other enhancements you want to make are most welcome.

Simon

> JMS Binding does not conform to the specification when selecting the opeartion to invoke
> ----------------------------------------------------------------------------------------
>
>                 Key: TUSCANY-1834
>                 URL: https://issues.apache.org/jira/browse/TUSCANY-1834
>             Project: Tuscany
>          Issue Type: Bug
>          Components: Java SCA JMS Binding Extension
>    Affects Versions: Java-SCA-1.0
>         Environment: SVN Revision #579118
> Linux
>            Reporter: Mark Combellack
>            Assignee: Simon Laws
>             Fix For: Java-SCA-Next
>
>         Attachments: JMSInvokeOperation.patch, JMSInvokeOperationTest.patch
>
>
> Currently, the way that the JMS Binding selects a method to invoke is not compliant with the SCA JMS Binding specification. Currently it always uses the scaOperationName parameter to find the operation This is option 2 in the specifications (lines 205 & 206 - see below)
> The JMS Binding specification says:
> 197    1.5 Default Operation Selection and Data Binding behavior
> 198    This section describes the default behavior for operation selection and data binding for a JMS
> 199    binding.
> 200    1.5.1 Default Operation Selection
> 201    When receiving a request at a service, or a callback at a reference, the native operation name is
> 202    determined as follows:
> 203    • If there is only one operation on the service's interface, then that operation is assumed as
> 204    the native operation name.
> 205    • Otherwise, if the JMS user property "scaOperationName" is present, then its value is used as
> 206    the native operation name.
> 207    • Otherwise, the native operation name is assumed to be "onMessage".

-- 
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