You want to generate the wsdl as part of the maven build, so that you could deploy it to a repo. I have never used the code-first approach with Maven, but I'm thinking that the wsgen mojo [1] should do what you want. Just specify that the wsdl should be generated.
/Anders [1] http://jax-ws-commons.java.net/jaxws-maven-plugin/wsgen-mojo.html On Mon, Nov 14, 2011 at 12:21, rop <rop...@gmail.com> wrote: > Need some advice on how to setup maven-build > of the client-jar for java-first webservices... > > Previously, I have been working with wsdl-first webservices, > where you simply save the wsdl in version-control > and then generate the java client classes from it. > > But now I have switched to another project, > where most webservices are already existing as *java-first*, > and we should now convert the builds from Ant to Maven. > > What is the best way to set this up in maven and version-control > to ensure you get the latest version of the wsdl? > > Obviously you dont want to save the wsdl into version-control, > since it is generated at runtime... > > I guess one way is in your maven-build to start app-server on localhost, > deploy the webservice to it, > then build the client-jar from the localhost-url. > Problem is the build might then fail if some dependencies > (db-connections, other webservice, etc) are not available at build-time. > > So is there some better way to do this? > > > -- > View this message in context: > http://maven.40175.n5.nabble.com/How-setup-java-first-webservice-client-jar-in-Maven-tp4990484p4990484.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
