Re: Packaging JAX-WS service implementation and client API
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 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
Re: Packaging JAX-WS service implementation and client API
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
Re: Packaging JAX-WS service implementation and client API
separate modules! /Anders On Thu, Aug 18, 2011 at 09:39, Asplund Marko wrote: > Hi, > > I'm using the jaxws-maven-plugin to build a JAX-WS webservice implementation > (packaged as an EJB jar). > The service contract and message type definitions are stored in src/wsdl and > they're packaged in META-INF/wsdl in a jar. > This is working fine, but now I need generate a Java client API package that > would only include JAXB generated classes and WSDL/XSD. > > How should I use Maven to create both the webservice implementation and > client API packages from a single module? > Or should I split the artefacts to separate modules? > > > marko > > - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
Packaging JAX-WS service implementation and client API
Hi, I'm using the jaxws-maven-plugin to build a JAX-WS webservice implementation (packaged as an EJB jar). The service contract and message type definitions are stored in src/wsdl and they're packaged in META-INF/wsdl in a jar. This is working fine, but now I need generate a Java client API package that would only include JAXB generated classes and WSDL/XSD. How should I use Maven to create both the webservice implementation and client API packages from a single module? Or should I split the artefacts to separate modules? marko
