Hi, I'm observing the wsdl/wsdl2 service section as follows,
wsdl2 : <wsdl2:service name="echo" interface="tns:ServiceInterface"> <wsdl2:endpoint name="echoHttpEndpoint" binding="tns:echoHttpBinding" address="http://10.100.1.192:9762/services/echo.echoHttpEndpoint"/> <wsdl2:endpoint name="echoHttpSoap11Endpoint" binding="tns:echoSoap11Binding" address=" http://10.100.1.192:9762/services/echo.echoHttpSoap11Endpoint"/> <wsdl2:endpoint name="echoHttpsEndpoint" binding="tns:echoHttpBinding" address="https://10.100.1.192:9443/services/echo.echoHttpsEndpoint"/> <wsdl2:endpoint name="echoHttpsSoap12Endpoint" binding="tns:echoSoap12Binding" address=" https://10.100.1.192:9443/services/echo.echoHttpsSoap12Endpoint"/> <wsdl2:endpoint name="echoHttpsSoap11Endpoint" binding="tns:echoSoap11Binding" address=" https://10.100.1.192:9443/services/echo.echoHttpsSoap11Endpoint"/> <wsdl2:endpoint name="echoHttpSoap12Endpoint" binding="tns:echoSoap12Binding" address=" http://10.100.1.192:9762/services/echo.echoHttpSoap12Endpoint"/> </wsdl2:service> wsdl: <wsdl:service name="echo"> − <wsdl:port name="echoHttpSoap11Endpoint" binding="ns:echoSoap11Binding"> <soap:address location=" http://10.100.1.192:9762/services/echo.echoHttpSoap11Endpoint"/> </wsdl:port> − <wsdl:port name="echoHttpsSoap11Endpoint" binding="ns:echoSoap11Binding"> <soap:address location=" https://10.100.1.192:9443/services/echo.echoHttpsSoap11Endpoint"/> </wsdl:port> − <wsdl:port name="echoHttpsSoap12Endpoint" binding="ns:echoSoap12Binding"> <soap12:address location=" https://10.100.1.192:9443/services/echo.echoHttpsSoap12Endpoint"/> </wsdl:port> − <wsdl:port name="echoHttpSoap12Endpoint" binding="ns:echoSoap12Binding"> <soap12:address location=" http://10.100.1.192:9762/services/echo.echoHttpSoap12Endpoint"/> </wsdl:port> − <wsdl:port name="echoHttpEndpoint" binding="ns:echoHttpBinding"> <http:address location=" http://10.100.1.192:9762/services/echo.echoHttpEndpoint"/> </wsdl:port> − <wsdl:port name="echoHttpsEndpoint" binding="ns:echoHttpBinding"> <http:address location=" https://10.100.1.192:9443/services/echo.echoHttpsEndpoint"/> </wsdl:port> </wsdl:service> As you can see the address would show like, http://10.100.1.192:9762/services/echo.echoHttpEndpoint Is this the intended behaviour? When I debug the listeners, it will give the proper endpoint address as ( http://10.100.1.192:9762/services/echo) but in the wsdl, the endpoint address is appended with the associated binding name. Saminda On Wed, Apr 16, 2008 at 8:45 PM, Davanum Srinivas <[EMAIL PROTECTED]> wrote: > -----BEGIN PGP SIGNED MESSAGE----- > Hash: SHA1 > > Indika, > > Will this work for you? Please check > > http://svn.apache.org/viewvc?rev=648716&view=rev > > - -- dims > > > indika kumara wrote: > | Hi Dims > | > | A minor thing , that appears when I am testing the synapse. > | > | In maven repositories , there is only .mar artifact of the mex module > and > | can't find .jar file for this module. In synapse,we only load classes > from > | jars. We can change the scripts to load classes from .mar files as well > , > | but it is more easy and convenient if there is a .jar artifact of the > mex > | module in the maven repositories. Is it possible? > | > | Thanks > | > | Indika > | > -----BEGIN PGP SIGNATURE----- > Version: GnuPG v1.4.5 (Cygwin) > > iD8DBQFIBhgUgNg6eWEDv1kRApGZAJwJIIIEgzLWJFUDSAJ+3dfXSHgYbgCfXFjW > 4dZUZZnNM3bqIVRll+8ypx4= > =Ammr > > -----END PGP SIGNATURE----- > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] > > -- Saminda Abeyruwan Senior Software Engineer WSO2 Inc. - www.wso2.org
