Give access to WSDL operation in proxy based mediations
-------------------------------------------------------

                 Key: SYNAPSE-204
                 URL: https://issues.apache.org/jira/browse/SYNAPSE-204
             Project: Synapse
          Issue Type: Improvement
          Components: Proxy Services
    Affects Versions: NIGHTLY
            Reporter: Andreas Veithen


I'm building a proxy service that executes an XSLT mediation where there is no 
one-to-one mapping between the operations defined by the proxy and the 
operations invoked on the target. Actually the proxy defines several operations 
that all execute the same operation on the target (with different input). 
Therefore the XSL transformation for the response requires knowledge about the 
original request, namely the operation invoked. While it is possible to do this 
based on the name of the element in the SOAP body of the original request, it 
would be easier if the mediation had access to the name of the operation 
invoked on the proxy. Axis easily gives access to this information through 
MessageContext#getAxisOperation. The information is available if the proxy 
service has a publishWSDL element. As far as I can see, Synapse doesn't expose 
this information to the mediation.

I propose to modify the get-property function to expose this information in a 
similar way to what is done e.g. for the WSA-Action. Since the operation is 
identified by a QName and this type is not supported by Jaxen, actually two new 
properties would be introduced: 'OperationName' and 'OperationNamespace'. Only 
modification of GetPropertyFunction and SynapseConstants (to define the 
property names) is required to implement this.

Attached is a proposed patch implementing this change.

-- 
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: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Reply via email to