You are viewing a plain text version of this content. The canonical link for it is here.

Posted to dev@airavata.apache.org by "Lahiru Gunathilake (JIRA)" <ji...@apache.org> on 2011/08/22 21:44:29 UTC

[jira] [Resolved] (AIRAVATA-50) Keep the same ws-messenger client in all over the airavata

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

Lahiru Gunathilake resolved AIRAVATA-50.
----------------------------------------

    Resolution: Fixed

> Keep the same ws-messenger client in all over the airavata
> ----------------------------------------------------------
>
>                 Key: AIRAVATA-50
>                 URL: https://issues.apache.org/jira/browse/AIRAVATA-50
>             Project: Airavata
>          Issue Type: Improvement
>          Components: WS-Messenger
>         Environment: mac
>            Reporter: Lahiru Gunathilake
>
> I can see two set of client implementations(MsgBrokerClient and WsmgClientAPI) in ws-messenger and they are performing the same functionality and one is much more cleaner than the other one. I think we need to use one client implementation across the product and motivate clients to use the newly implemented MsgBrokerClient implementation.
> I have to remove all the places where we use WsmgClientAPI in ws-messenger and other airavata components.
> Regards
> Lahiru

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