Brad Davis wrote:
Yes, this is deliberate at present because we publish the derived WSDL and validate the configuration at that point. As mentioned earlier in the week though, this is easy to work around by using a local copy of the WSDL and will give you the behaviour you require.
I am saying if this is deliberate, we should fix it because it is a design flaw. That is why I opened the support ticket.
I'm sorry, I can't resist responding. How is this a design flaw? If we went with a lazy approach, then we would have a deployed service for which we would not be able to expose WSDL for! We need to pull in the WSDL on initialization so we can transform it and provide it to consumers of the ESB. If we went the lazy way, we would get more bug reports from people saying "WSDL contract unavailable!"