-
1. Re: Problems loading WSDL with SOAPProxy
dward Apr 6, 2010 3:54 PM (in response to doudl)Leon,
The "classpath://" part of the wsl property value is stripped off before classloading. So, if you don't want the resource to be loaded relatively, you need to add an extra "slash" to make the value "absolute". So, instead of "classpath://wsdl/NotifyConsumer.wsdl" use "classpath:///wsdl/NotifyConsumer.wsdl" (3 slashes not 2).
Let me know how it goes. Thanks,
David
-
2. Re: Problems loading WSDL with SOAPProxy
doudl Apr 7, 2010 8:31 AM (in response to dward)Thanks, the additional "/" fixed it. Sorry I didn't catch on to that fact when looking at the code or documentation.
Just curious, is there an example when you would want to use just two slashes?
-
3. Re: Problems loading WSDL with SOAPProxy
dward Apr 8, 2010 10:14 AM (in response to doudl)Probably not. But I just wanted to be consistent for what an "absolute" path looks like. For example, "file:///home/dward" is what I type into my web browser when I want to open my home directory.
-
4. Re: Problems loading WSDL with SOAPProxy
doudl Apr 15, 2010 5:17 PM (in response to dward)After restarting the server I noticed the WSDL was no longer loading. If I "touch" the jboss-esb.xml file and trigger a hot redeploy the WSDL does load and I can access it via a browser pointed at the ESB.
At first I suspected a classloading issue, so I reconfigured the path of the WSDL to use file:///path/to/file.wsdl (notice the three slashes). This did not work on server startup, but triggering a hot redploy did cause WSDL to load.
Perhaps this is a startup order problem? I didn't see any errors in the log file though.
-
5. Re: Problems loading WSDL with SOAPProxy
doudl Apr 15, 2010 5:25 PM (in response to doudl)Sorry about posting without checking the other new postings. I suspect my problem is related to:
-
6. Re: Problems loading WSDL with SOAPProxy
dward Apr 16, 2010 9:04 AM (in response to doudl)No worries, Leon. Yes, JBESB-3255 documents the most likely cause of your issue. Please upgrade to ESB 4.8 and verify your issue has been fixed. Thank you.