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
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
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
