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 2011/07/06 11:45:18 UTC

[jira] [Closed] (TUSCANY-3881) Make the handling of binding context in the Axis2 WS binding more consistent

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

Simon Laws closed TUSCANY-3881.
-------------------------------

    Resolution: Fixed

> Make the handling of binding context in the Axis2 WS binding more consistent
> ----------------------------------------------------------------------------
>
>                 Key: TUSCANY-3881
>                 URL: https://issues.apache.org/jira/browse/TUSCANY-3881
>             Project: Tuscany
>          Issue Type: Improvement
>    Affects Versions: Java-SCA-2.0-M5
>            Reporter: Simon Laws
>            Assignee: Simon Laws
>            Priority: Minor
>             Fix For: Java-SCA-2.0
>
>
> On the reference side of the Axis2 binding the operation client is used as the binding context. On the service side the "In" message context. This is not as clear and consistent as it could be. I'd like to extend the code to use an aggregate context something like...
> Axis2Context
>     OpertationClient
>     OutMessageContext
>     InMessageContext

--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira