Oh. Right. Client side uses a URL and not a string. Forgot about
that. :-(
Yea, the only real option is to pass:
-wsdlLocation ""
(empty string) which with 2.1.3 I think will not generate the URL at all.
You would then need to do the getResource(...) thing yourself to find the
appropriate URL.
Dan
On Friday 31 October 2008 1:34:40 pm sreuland wrote:
> Hello Dan, thanks for reply, I've tried 'classpath:my.wsdl' or
> 'classpath:/my.wsdl' as wsdlLocation param to wsdl2java. The static
> initializer url = new java.net.URL("classpath:my.wsdl"); in generated
> Service class throws a MalFormed exception. The only way I've managed to
> get the URL() constructor to find my.wsdl is when i specify a 'file' scheme
> such as 'file:my.wsdl', then the URL constructor finds the file but it has
> to be relative to the starting directory of the jvm(not embedded in a jar).
> I figured if code generation in wsdl2java could recognize 'classpath:'
> scheme in wsdlLocation param and generate url =
> Service.class.getClassLoader().getResource("my.wsdl"); instead of try {
> url = new URL("my.wsdl"); } catch (MalformedURLException e) { } then
> runtime should find wsdl from classpath since java.net.URL constructor
> won't.
--
Daniel Kulp
[EMAIL PROTECTED]
http://dankulp.com/blog
