Asankha, thank you very much, it looks like this will work. Using '*useOriginalwsdl*' and '*modifyUserWSDLPortAddress*' (correctly...), we now get this soap webservice location:
<soap:address location="http://SERVERNAME:8280/services/ValidateCLI"/> where *8280 *is the port on which Synapse runs. I would very much like to use *TPMonitor *to spy on both the GET wsdl call, as well as the webservice call itself. Is it possible to have the (proxied) wsdl, returned by Synapse, to specify a different port number than 8280? Such that I can configure a Synapse redirection? Or perhaps a different server name? Many thanks for all your help! Henrik 2008/12/11 Asankha C. Perera <[EMAIL PROTECTED]> > For the benefit of anyone looking at this later, the solution to this > question was: > > Move the <parameter ...> elements as children to the <proxy> element and > not to the <publishWSDL...> > Then you can use any WSDL you like, as Synapse just shows what you specify > without modifying or validating it > > cheers > asankha > > > Asankha C. Perera wrote: > >> Hi Henrik >> >>> A complete, standalone test case can be downloaded from here: >>> http://sparklingideas.co.uk/synapse.test.case.henrik.zip* [28 MB]* >>> >>> For convenience, I have also attached to this email: >>> >>> 1. /validateCli.wsdl/ [Original WSDL file] >>> 2. /proxied_validateCli.wsdl /[Proxied WSDL file, served up by Synapse] >>> 3. /synapse.xml/ >>> 4. /stack.trace/ [stacktrace from the wsimport stubs, when >>> "TelewestBindingPort" can not be found] >>> 5. /generated.java.source.sample.java/ [File generated by wsimport. >>> Note the hardcoded binding name "TelewestBindingPort"] >>> >>> Can you also attach the referenced XSD's so that I can just try starting >> up your configuration? If your original WSDL is displayed your problem is >> solved right? >> >> cheers >> asankha >> >> > > -- > Asankha C. Perera > http://adroitlogic.org > > http://esbmagic.blogspot.com > >
