Mailing-List: contact axis-c-dev-help@ws.apache.org; run by ezmlm
Precedence: bulk
Reply-To: "Apache AXIS C Developers List" <axis-c-dev@ws.apache.org>
Message-ID: <33041402.1175148865719.JavaMail.jira@brutus>
Date: Wed, 28 Mar 2007 23:14:25 -0700 (PDT)
From: "Samisa Abeysinghe (JIRA)" <jira@apache.org>
To: axis-c-dev@ws.apache.org
Subject: [jira] Assigned: (AXIS2C-226) Remove the MEP client from API and
 move the relavant logic to operation client
In-Reply-To: <2090331.1154652434536.JavaMail.jira@brutus>
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit


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

Samisa Abeysinghe reassigned AXIS2C-226:
----------------------------------------

    Assignee: Samisa Abeysinghe

> Remove the MEP client from API and move the relavant logic to operation client
> ------------------------------------------------------------------------------
>
>                 Key: AXIS2C-226
>                 URL: https://issues.apache.org/jira/browse/AXIS2C-226
>             Project: Axis2-C
>          Issue Type: Improvement
>          Components: core/clientapi
>    Affects Versions: Current (Nightly)
>            Reporter: Samisa Abeysinghe
>         Assigned To: Samisa Abeysinghe
>             Fix For: 1.0.0
>
>
> operation client implementation uses some of the API of MEP client. The logic could easily be moved to operation client from MEP clent to reduce duplication. After this move of API, MEP client should be obsoleted.

-- 
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: axis-c-dev-unsubscribe@ws.apache.org
For additional commands, e-mail: axis-c-dev-help@ws.apache.org