[jira] Commented: (AXIS2-279) Having MessageContext.remove() method to discared discriptions

["Eran Chinthaka (JIRA)" <ji...@apache.org>]

    [ http://issues.apache.org/jira/browse/AXIS2-279?page=comments#action_12331958 ] 

Eran Chinthaka commented on AXIS2-279:
--------------------------------------

By definition, message context is per message per MEP. Its not meant to be used for multiple invocations. 

So messageContext.remove() seems, at leat to me, is you gonna re-use the same thing again which violates the above  concept.

I think what you have in mind is to use this message context for Synapse too. IMO, rather than tweaking here, better to have a SynapseContext. But this is not the correct place to comment on this. Plese send a mail to Synapse dev and lets  start a thread there.

> Having MessageContext.remove() method to discared discriptions
> --------------------------------------------------------------
>
>          Key: AXIS2-279
>          URL: http://issues.apache.org/jira/browse/AXIS2-279
>      Project: Apache Axis 2.0 (Axis2)
>         Type: Improvement
>   Components: core
>     Versions: 0.93
>  Environment: Linux
>     Reporter: Saminda Wishwajith Abeyruwan
>     Priority: Minor

>
> There can be a situation where, one can use the existing MessageContext to call for engine.receive(messageContext) for invoke a different service. But, as this is the old MC, first we need to remove old  ServiceDescription and OperationDescription, and at some point set the new Service/OperationDescriptions. In order to do this, if we can have MessageContext.remove() would be very handy.

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
   http://issues.apache.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see:
   http://www.atlassian.com/software/jira