Asankha, As I told, since there was a conceptual change in axis2, the fault was on our side.
In detail the change is that, axis2 now reflects the exact WSDL as it is over the generated WSDL in WSDL bindings and WSDL ports. So if there are 2 bindings in the wsdl that we used to generate the service, axis2 will only add those two and nothing else and WSDL ports are the same. We need the vice-versa and need to change the bindings and the WSDL ports according to our transports. So I had to clear the bindings (AxisEndpoints map) from the generated service so that axis2 adds all the bindings from all the transports and the WSDL ports. Adding a unit test for this is pretty hard but should be able to do because we can keep a wsdl to generate a service and a copy of the WSDL of the generated service, so that we can do an XML comparison of the WSDL with the one we store. I will try to come up with a unit test for this. Thanks, Ruwan On Tue, Apr 15, 2008 at 1:45 PM, Asankha C. Perera <[EMAIL PROTECTED]> wrote: > Ruwan > > Was the fault on our side or on Axis2? Anyway would be good if we could > write a unit test for this scenario if at all possible.. > > > I guess this is a regression because that works fine with synapse 1.1.1 > > > > release. > > > > > > > > > > > asankha > -- Ruwan Linton http://www.wso2.org - "Oxygenating the Web Services Platform"
