On Wed, 2005-05-04 at 15:57 +0600, Chathura Herath wrote: > Hi Deepal, Glen, all > > IMO We will need one of "OperationContext" or "MEPContext"(That is Rename > the MEPContext already there to OperationContext or leave it as it is). I > don't see strong reasons why we need both OperationContext and MEPContext. > > As far as I know the AxisOperation is there and continue to be there to > represent the deployment time configuration of the WSDL Operations, and > don't think there are any arguments over that. > > If you want to stick a module into an Operation, fine. Put it in the > AxisOperation along with other deployment information of the Operation.
+1 - when one engages a module for a specific operation, that's typically for all usages of that operation. Then that engagement needs to be recorded in AxisOperation. However, in the future, its possible to have a dynamic policy negotiation type thing that will engage a certain module just for a specific usage of a given operation rather than for all usages. Even in that case we have the vehicle to address it: just record that in the MepContext (which represents the usage of an operation). Sanjiva.
