For the wsdl location, you can try something like "classpath:/blah/my.wsdl". I'm not sure if that will work or not.
However, even if it DOES work (after briefly looking at the code, I'm not really sure if it will or will not work. Log a bug if it doesn't), it will re-run/regenerate the code every time you type "mvn install" as it won't be able to detect if the wsdl has changed or not. Thus, I suggest using the dependency plugin to "unpack" the dependency into a dir in target and then configure the cxf plugin to generate from there. dependency will not unpack of the jar hasn't changed, and thus we won't re-run. Dan On Mon August 3 2009 11:57:18 am shsebast wrote: > I am collecting all the wsdl's in my project in a jar file and deploying it > on the maven repository. I have read earlier posts which suggests that cxf > maven tooling for wsdl2java can grab wsdl from a jar file in the classpath. > Can anyone help me with the syntax for doing this. > > I am referring to the below email sent on 09 Oct 2008 from Dan Kulp to a > question regarding using WSDL as Maven artifact > > "If the wsdl is in a jar, I know the CXF wsdl2java tooling (maven plugins) > can > grab the wsdl out of the jar and generate code from it. Thus, a "common" > jar could have the wsdl and the common generated stuff (like the jaxb > types, the service interface, etc...) and the others could use it." > > Thanks > S. Sebastian -- Daniel Kulp [email protected] http://www.dankulp.com/blog
