synapse-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Andreas Veithen <andreas.veit...@gmail.com>
Subject Re: Proposal to introduce a new attribute to WSDLEndpoint configuration
Date Sun, 17 May 2009 15:46:14 GMT
Probably the first step would be to check if the current Synapse
architecture supports this, and if not, what would be the changes
required. Do you already have any ideas?

Andreas

On Sat, May 16, 2009 at 15:19, Supun Kamburugamuva <supun06@gmail.com> wrote:
> Hi all,
>
> If everybody agress I would like to come up with a patch for this.
>
> Our plan is to create an axis service from the WSDL.
>
> Do the logic in Axis2 dispatchers to find out the operation at run time.
>
> Do the client call with this operation.
>
> Thanks,
> Supun..
>
> On Sat, May 16, 2009 at 3:58 PM, Andreas Veithen <andreas.veithen@gmail.com>
> wrote:
>>
>> Yes, in order to identify the operation for an outgoing request, the
>> WSDL endpoint should apply the same rules as the dispatchers would
>> apply for an incoming request.
>>
>> Andreas
>>
>> On Sat, May 16, 2009 at 07:04, Supun Kamburugamuva <supun06@gmail.com>
>> wrote:
>> > Andreas,
>> >
>> > Did you mean manually doing what dispatchers does within the WSDL
>> > endpoint?
>> >
>> > Supun..
>> >
>> > On Fri, May 15, 2009 at 1:01 PM, Andreas Veithen
>> > <andreas.veithen@gmail.com>
>> > wrote:
>> >>
>> >> Supun,
>> >>
>> >> 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.
>> >>
>> >> Andreas
>> >>
>> >> On Fri, May 15, 2009 at 08:26, Supun Kamburugamuva <supun06@gmail.com>
>> >> 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: dev-unsubscribe@synapse.apache.org
>> >> For additional commands, e-mail: dev-help@synapse.apache.org
>> >>
>> >
>> >
>> >
>> > --
>> > Software Engineer, WSO2 Inc
>> > http://wso2.org
>> > supunk.blogspot.com
>> >
>> >
>> >
>>
>> ---------------------------------------------------------------------
>> To unsubscribe, e-mail: dev-unsubscribe@synapse.apache.org
>> For additional commands, e-mail: dev-help@synapse.apache.org
>>
>
>
>
> --
> Software Engineer, WSO2 Inc
> http://wso2.org
> supunk.blogspot.com
>
>
>

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@synapse.apache.org
For additional commands, e-mail: dev-help@synapse.apache.org


Mime
View raw message