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 Thu, 14 May 2009 09:33:33 GMT
On Thu, May 14, 2009 at 11:26, Amila Suriarachchi
<amilasuriarachchi@gmail.com> wrote:
>
>
> On Thu, May 14, 2009 at 1:41 PM, Andreas Veithen <andreas.veithen@gmail.com>
> wrote:
>>
>> If we build an AxisService object from the WSDL, it is fairly easy to
>> determine the operation at runtime (using
>> AxisService#getOperationBySOAPAction and
>> AxisService#getOperationByMessageElementQName). Axis2 also has the
>> required methods to calculate the policy applicable for a given
>> operation. The question is how this would fit into the Synapse
>> architecture, considering that the policies on endpoints are set
>> during startup.
>
> I also feel this should be the correct way.
> Only thing which have to set at synapse level is the rampart specific
> polices to give keystore etc ...
>
> Currently if some one creates an end point,  pointing to a wsdl how synapse
> handle it?
>
> Does it creates the AxisService object using WSDL112AxisService builder or
> use an annoymous
> AxisService to send the message?
>
> thanks,
> Amila.
>

I think Synapse uses lower level APIs (WSDL4J) to parse the WSDL and
only extracts the endpoint address. Policy information is not
extracted and must be set explicitly.

Andreas

>
>>
>>
>> Andreas
>>
>> On Wed, May 6, 2009 at 06:12, Supun Kamburugamuva <supun06@gmail.com>
>> wrote:
>> > Andreas,
>> >
>> > Axis2 traverse the WSDL and attach the policies to the description
>> > hierachy.
>> > At the run time it caculates the policy. But this method is not possible
>> > with Synapse, since we are using predefined axis2 services and
>> > operations in
>> > the Synapse client side.
>> >
>> > On the other hand it is difficult to find the operation (which is
>> > normally
>> > done by Axis2 dispatchers) from the incoming message in the client side.
>> > Even if we get to know the operation some how, we have to calculate the
>> > policy at run time. We may need to traverse the WSDL again or we may
>> > have to
>> > store all the policies and information in the WSDL for calculating this
>> > at
>> > run time.
>> >
>> > At the moment WSDL endpoint has an option for specifying in message
>> > policy
>> > and out message policy. If the operation is determined at the run time,
>> > theoretically these policies should vary according to the incoming
>> > message.
>> >
>> > Thanks,
>> > Supun..
>> > WSDL Endpoint allows the user to specify the in policy and out policy.
>> > On Tue, May 5, 2009 at 7:05 PM, Andreas Veithen
>> > <andreas.veithen@gmail.com>
>> > wrote:
>> >>
>> >> 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 <supun06@gmail.com>
>> >> 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: 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
>>
>
>
>
> --
> Amila Suriarachchi
> WSO2 Inc.
> blog: http://amilachinthaka.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