I second Kalle about the fact that wsdl are too small entities to elect them artifacts. In my current project I keep the wsdl in the service implementation artifact and I package the wsdl with clients stubs in another artifact. The client artifact being built with the following sequence : unpack the wsdl from the service artifact using maven-dependency-plugin and then generate the client stubs with the appropriate maven plugin.
Paul Le Thursday 09 October 2008 19:02:45 Hayes, Peter, vous avez écrit : > 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 <http://www.linkedin.com/in/petehayes> > Architecture & Shared Technology Services | Fidelity Investments > Management Technology --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
