be aware that for the full functionality of JAXWS 2.2 you need JDK 7.0 installed.
@Requestwrapper @Responswrapper @Addressing . . . in any case, there is an axis2-1.6.1 class which calls up on a interface for partName() (see my previous posts in this regards, and the sample/JAXWSCalculator) javac's compiles and maven builds nicely, and surefire test are all running but you will get a stack dump when annotations as shown above are used on top of a JDK 6.0 installation. Josef Von: Philippe A. [mailto:futhar...@gmail.com] Gesendet: Donnerstag, 26. April 2012 15:57 An: java-user@axis.apache.org Betreff: Re: Completly lost 2012/4/4 Philippe A. <futhar...@gmail.com> I still wish I could avoid policy duplication on the client side. Ideally I would like to write a rampart.xml with no policy inside and assign that config to my generated service client. I went a step further and gave up using wsdl2java. Writing an Axis client by hand isn't that hard. The advantage of wsdl2java depends a lot on the number and complexity of operations you have to support. I only have a handful. The next logical step for me would be to give JAXWS a try. -- Philippe
