If your project is currently using
"/{classPath}/{methodPath}" you will have to create java instance of generated client's {classPath} instance first and get reference to {methodPath} inner class instance from it in order for client to build URI's appropriately.
<dependency>and you are looking for stable version of a plugin, you should be using following:
<groupId>org.jvnet.ws.wadl</groupId>
<artifactId>wadl-maven-plugin</artifactId>
<version>1.1-SNAPSHOT</version>
</dependency>
<groupId>org.jvnet.ws.wadl</groupId>this is the most recent and least bogous version of plugin. Nothat you will have to refactor code if you was using client generated by wadl plugin. Also note that to reach endpoints with compound paths like
<artifactId>wadl-client-plugin</artifactId>
<version>1.1.3</version>
"/{classPath}/{methodPath}" you will have to create java instance of generated client's {classPath} instance first and get reference to {methodPath} inner class instance from it in order for client to build URI's appropriately.
Thank you, very nice post.
ReplyDelete