Hi Alexandre, It seems like an issue which has been introduced by the migration of the axis2 version from 1.4 to SNAPSHOT. Can you please raise a JIRA for this. We will fix this ASAP....
Thanks, Ruwan On Wed, Apr 9, 2008 at 9:28 PM, alexandre_garino < [EMAIL PROTECTED]> wrote: > > Hi, > > I built synapse from the rev 646352. I set up a new proxy from this xml > fragement. > > <proxy name="KpsProxy" transports="http" startOnLoad="true"> > <target> > <inSequence> > <send> > <endpoint> > <address uri="https://www.xxxxx.xxx/kps.asmx";> > <enableAddressing/> > <enableSec policy="policy.kps"/> > </address> > </endpoint> > </send> > </inSequence> > <outSequence> > <send/> > </outSequence> > </target> > <publishWSDL uri="https://www.xxxxx.xxx/kps.asmx?wsdl"/> > </proxy> > > When I retrieve the WSDL through synapse (e.g. > http://10.130.30.202:8080/soap/KpsProxy?wsdl) I noticed that the service > element is not properly updated. Location attributes remain unchanged. > > <wsdl:service name="KpsProxy"> > <wsdl:port name="KPSSoap" binding="tns:KPSSoap"> > <soap:address location="https://www.xxxxx.xxx/kps.asmx"; /> > </wsdl:port> > <wsdl:port name="KPSSoap12" binding="tns:KPSSoap12"> > <soap12:address location="https://www.xxxxx.xxx/kps.asmx"; /> > </wsdl:port> > </wsdl:service> > > I guess this is a regression because that works fine with synapse 1.1.1 > release. > > Regards, > Alexandre > > -- > View this message in context: > http://www.nabble.com/WSDL-Generation-tp16588436p16588436.html > Sent from the Synapse - User mailing list archive at Nabble.com. > > -- Ruwan Linton http://www.wso2.org - "Oxygenating the Web Services Platform"
