ws-kandula-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Christian Connert (JIRA)" <>
Subject [jira] Updated: (AXIS2-4548) WSDL11ToAxisServiceBuilder ( client side) doesn't correctly build the bindings
Date Tue, 04 May 2010 14:23:56 GMT


Christian Connert updated AXIS2-4548:


Hi Mathew,

when I created the just uploaded test case, I had to admit that my first description is not
precise enough. 

The exact problem is that WSDL extensions, like in the sample case ws:policy reference attachments
at the message level, are not correctly attached at the corresponding AxisBindingMessage object.

For instance for a request / response exchange pattern the message level policy (
is always attached at the incoming message (see sample output).
In the case of a one way exchange pattern the AxisBindingMessage object does not exist in
a client side service and thus the policy information is lost.

The reason for this behaviour is that the WSDL11ToAxisServiceBuilder.populateBinding(...)
method does not consider the isServerSide attribute during the parsing step and thus it actually
uses the wrong or in case of a one way message no bindings.

The appended tests outputs some basic information about the service and the attached policies
references at the binding level for a simple service. The server side service behave correctly
but not the client side service. 

I hope now this description is precise enough.


> WSDL11ToAxisServiceBuilder ( client side) doesn't correctly build the bindings
> ------------------------------------------------------------------------------
>                 Key: AXIS2-4548
>                 URL:
>             Project: Axis2
>          Issue Type: Bug
>          Components: kernel
>            Reporter: Christian Connert
>             Fix For: 1.5, 1.4.1, 1.4
>         Attachments:, UtilService.wsdl
> The WSDL11ToAxisServiceBuilder doesn't respect the isServer attribute when building the
bindings, thus the bindings for a client AxisService will be switch and even worse in case
of a one-way operation missing.

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:
For additional commands, e-mail:

View raw message