Folks, Simon Laws wrote:
Oops, well spotted, it should have been as you suggest... <binding.ws requires="transport.jms"/> It doesn't do any harm adding the WSDL but it works without although currently I don't expect the WSDL definition model has the correct JMS entries in it, i.e. I haven't written the code to make that happen. Interesting question here about which piece of configuration wins. I guess that if you have gone to the trouble to specify the WSDL over and above the intent the WSDL should win.
The binding.ws spec basically says that the WSDL wins if it is present.
Regards Simon
--------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
