You could even separate out the wsdl/xsd in its own artifact(s). That's what I normally recommend as it will then allow the client to use whatever ws service and xml binding technology they like.
/Anders On Mon, Aug 22, 2011 at 06:50, Asplund Marko <marko.aspl...@ixonos.com> wrote: > > Anders Hammar wrote: >> separate modules! > > Yes, that's how i ended up solving it. > I created X-service API (XSD, WSDL, JAXB classes) and X-service > implementation modules. > The service implementation module only contains the implementation code > and it depends on the service API module and gets the service contract > definition from there. The API module is distributed via an artifact > repository to allow module development lifecycles to be more effectively > separated. > > > marko > > > > --------------------------------------------------------------------- > To unsubscribe, e-mail: users-unsubscr...@maven.apache.org > For additional commands, e-mail: users-h...@maven.apache.org > > --------------------------------------------------------------------- To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
