You could either deploy the wsdl in a jar file (or zip or whatever) or deploy it as is. Personally I've gone the path of having the wsdl deployed as is to the repo. Ultimately (IMHO), the wsdl should be in a separate project so that is the primary artifact. A client using your ws doesn't care about anything but the wsdl.
/Anders On Tue, Nov 15, 2011 at 09:55, rop <rop...@gmail.com> wrote: > Thanks Anders, > Just to clarify... > So the serverside webservice-project puts the wsdl in a jar-file, which is > deployed to Nexus? > And the client-project can then read that wsdl from the classpath and > generate the client-jar? > Is that what you have in mind? > > > -- > View this message in context: > http://maven.40175.n5.nabble.com/How-setup-java-first-webservice-client-jar-in-Maven-tp4990484p4993782.html > Sent from the Maven - Users mailing list archive at Nabble.com. > > --------------------------------------------------------------------- > 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
