synapse-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Andreas Veithen <>
Subject Re: Proposal to introduce a new attribute to WSDLEndpoint configuration
Date Fri, 15 May 2009 08:01:39 GMT

If you look at the code of the relevant dispatchers, you will see that
they simply delegate to AxisService#getOperationBySOAPAction and
AxisService#getOperationByMessageElementQName to find the operation.
So we can easily find the operation without invoking the dispatchers.


On Fri, May 15, 2009 at 08:26, Supun Kamburugamuva <> wrote:
> If we build the Axis service from the WSDL, I think it is reusable across
> multiple requests. So we do not need to create the service for each
> request.
> Synapse client side gets the whole SOAP envelope. At this point synapse
> doesn't know about the operation. Only way we can find out the operation
> is to send this message through the Axis2 dispatchers. But Axis2 client side
> send cannot find the operation from the SOAP envelope, becuase it is the
> out-flow of the Axis2 and dispatchers are not in the out flow.
> So even if we use Axis2 code to generate a client from the WSDL, we need to
> find the operation manually using the synapse configuration. As I have
> mentioned in the previous mail we can set the operation as a property and
> WSDL endpoint can pick this property. To find out the operation we can use a
> mediator like filter.
> Supun..

To unsubscribe, e-mail:
For additional commands, e-mail:

View raw message