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
