Agreed however making the whole ESB deployment fail because of one errant Web Service seems severe.
It would be great if you had a property to allow me to fail, ignore, retry, use cache, construct on first request, etc.
Right now the code constructs temporary files to cache the WSDL, XSDs, failing back on the temp files would be acceptible under certain conditions.
Of course they would have to be named by category+service-name in order to resolve.
It would also be great if the ?wsdl request entered the pipeline first, this would have made it easier for me to do fixups on modular wsdls.
I will read the thread. Thanks.
BTW - I'm pushing some of these issues via redhat.com support too, sorry about the overlap.
!