Yeah, the SU order is significant. You need to put the jsr181 first, as the http component need the endpoint to be activated to be able to generate the wsdl (unless you also put the wsdl in the http SU).
On 10/31/06, Bernard Lupin <[EMAIL PROTECTED]> wrote:
Hi all, It seems that the order of the SUs in jbi.xml is important, but I can't figure how to choose it. I've a very simple example based on the old soap-binding example : If the binding-su (based on servicemix-http) is declared first, and engine-su (based on servicemix-jsr181) is declared second, I can't get the WSDL by entering "http://localhost:8192/Service";. If I reverse this order, my WSDL is well generated and showed in my browser. Note that in both case, the "client.html" test works fine and ping my entry. Is it a bug or do I have to define my SUs in a defined order ? Regards, Bernard -- View this message in context: http://www.nabble.com/order-of-SU-in-jbi.xml-tf2545309.html#a7092298 Sent from the ServiceMix - User mailing list archive at Nabble.com.
-- Cheers, Guillaume Nodet
