|WST Axis2 Client code generation / project update question [message #231072]
||Tue, 05 May 2009 19:47
Registered: July 2009
We've been using the Eclipse Axis2 Eclipse plugin with good results,
however we recently decided to try the WST plugin instead which led us to
For some reason, generating a client web service interface seems to bring
in the same artifacts of the Axis2 tooling that generating a server side
interface does; namely WebContent/axis2-web, modules, etc. We have not
been able to find out how to NOT generate all this.
We are also keeping the Axis2 libraries in the servlet container and do
not want to maintain them in every project. (Really not up for discussion)
So there is no need to maintain them in any particular project.
Any thoughts as to how to not pollute the project with all the extra
unnecessary cruft would be appreciated.
BTW: How is WTP related to WST? Rather confusing....
Powered by FUDForum
. Page generated in 0.06391 seconds