I support this idea. As the previous discussion shows, there are use-cases where WSDL files on its own are too small a fragment, but there are also other use-cases. For example for JSR 264 we used a tooling to generate the specification, which consisted purely of interfaces. We wanted to package them separately and create a jar file with all the JavaEE interfaces, one with tens of XML Schema and another one with WSDL files. All the packages describe the same interface from a functionality point of view, but allow for different interaction patterns and integration scenarios.
If you want to take a look at our project layout, look here: https://jsr264-public.dev.java.net/source/browse/jsr264-public/ It's still kind of crude, but the spec_model is generating all interfaces in a single artifact, which is then split in the spec_jvt, spec_xsd and spec_wsdl projects. Andreas [EMAIL PROTECTED] <mailto:[EMAIL PROTECTED]> mobile: +49 (175) 2664109; office: +49 (212) 2494 331; fax: +49 (212) 2494 334 Grünewalder Str. 29-31; 42657 Solingen Geschäftsführer: Peter Gierse, Mirko Novakovic und Rainer Vehns - Sitz der Gesellschaft: Solingen Registergericht: Amtsgericht Wuppertal, HRB 19214 Von: Hayes, Peter [mailto:[EMAIL PROTECTED] Gesendet: Donnerstag, 9. Oktober 2008 19:03 An: Maven Users List Betreff: WSDL as Maven artifact We are building web services and in our approach multiple maven projects would be consumers of the service WSDL in order to generate their server / client stubs. I think it would be good to have a project of packaging type wsdl and then have consumer projects depend on that artifact. Has anybody tried to do this or is there a better pattern for doing this? I found one reference on the web about this : http://myarch.com/using-maven-repository-as-web-services-registry Possibly the hard part would be integrating with existing wsdl2java plugins that expect a file path to the WSDL file. I would guess that I would have to customize one to automatically grab depencies of type wsdl and then pass them to the code generator. Peter Hayes LinkedIn Profile <http://www.linkedin.com/in/petehayes> Architecture & Shared Technology Services | Fidelity Investments Management Technology
