Supun, In principle, when the message is handed over to the WSDL endpoint it should contain enough information (either the SOAP action or the name of the payload element) to determine the operation, so there should be no need for an additional attribute. I say "in principle", because in practice this might be a bit tricky. It would be interesting to check if the logic that does this in Axis2 can be reused for this purpose.
Andreas On Tue, May 5, 2009 at 13:21, Supun Kamburugamuva <[email protected]> wrote: > Hi all, > WSDL endpoint has port and service as configuration parameters. From this > information we can find the service, port and binding from the WSDL. But > this information is not enough to find the operation. Because of this we > cannot calculate the complete policy when operation level and message level > policies are specified. It'll be really useful to introduce a new optional > attribute to the WSDL endpoint configuration. i.e. operationName which > allows us to calculate the complete policy. If all of you agree I would like > to implement this and contribute this to Synapse. > I really appreciate your opinions and concerns regarding this. > Thanks, > Supun.. > -- > Software Engineer, WSO2 Inc > http://wso2.org > supunk.blogspot.com > > > --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
