[ http://issues.apache.org/jira/browse/AXIS2-279?page=all ]
Deepal Jayasinghe resolved AXIS2-279:
-------------------------------------
Fix Version: 0.95
Resolution: Fixed
As I know Synapse has its own context called SynapseContext , so I think we do
not want to provide msg.remve(),
Saminda , I will resolve the issue if you feel you really want this feature pls
re-create a JIRA
> 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
> Fix For: 0.95
>
> 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
