Hello,
We have a multi-module Maven project that we are adding Axis2 to as a
dependency.
The axis2-kernel-1.6.2.pom has a dependency:
dependency
groupIdjavax.servlet/groupId
artifactIdservlet-api/artifactId
/dependency
This seems to conflict with a
Hi Todd,
Are you going to fork Axis2 release code ? if not you can specify
axis2-1.6.2 maven dependency as follows,
dependency
groupIdorg.apache.axis2/groupId
artifactIdaxis2/artifactId
version1.6.2/version
/dependency
Axis2 use maven dependency management to maintain the same
Shameera,
I created a small project on Github that demonstrates my problem.
https://github.com/chakatodd/axis2_dependency_woes
On Thu, Feb 6, 2014 at 1:59 PM, Shameera Rathnayaka
shameerai...@gmail.comwrote:
Hi Todd,
Are you going to fork Axis2 release code ? if not you can specify
Todd=
Thats because you have ADB code which is the default binding
WSDL2Java Test.wsdl
Im betting you didnt specify -Dxmlbeans to generate the code from wsdl2java
in which case you want the ADB code (comment out the axis-xmlbeans artifact as
dependency)
Thank you for the input Martin. Commenting out the axis-xmlbeans artifact
dependency caused further compilation errors. The code that is using Axis2
was generated by another group. I'll check with them to see what command
they used to generate the code.
-Todd
On Thu, Feb 6, 2014 at 9:19 PM,
The difference between the two is the version. For some reason, the servlet
API 3.x was imported into Maven central with a different artifact ID. That
is not something we control.
The version of the servlet API used by Axis2 is specified by a
dependencyManagement entry in the parent POM (it is 2
