jboss - Axis 2 dependency and geronimo jars in war file after built with maven -

I'm new to the axis, please be patient. I have prepared Java files from the WSDL endpoint, and in each Java file

apply org.apache.axis2.databinding.ADBBean {

whose This means that in the field of compilation, The dependence of axis2.jar in XM is required (please correct me if I am wrong).

But this axis2.jar dependency also downloads too many Geronimo files. But I'm using Jebos. I really do not want Garonimo files in my war.

Is it really necessary for these Geronimo jars? Or maybe I'm doing something wrong when specifying axis2.jar compile-time dependency in pm.xml?

  & lt; Dependency & gt; & Lt; Group & gt; Javax.servlet & lt; / Group & gt; & Lt; ArtifactId & gt; Servlet-api & lt; / ArtifactId> & Lt; Version & gt; 2.4 & lt; / Edition & gt; & Lt; Scope & gt; Provided & lt; / Scope & gt; & Lt; / Dependencies & gt; & Lt; Dependency & gt; & Lt; Group & gt; Org.apache.axis2 & lt; / Group & gt; & Lt; ArtifactId & gt; Axis2 & lt; / ArtifactId> & Lt; Version & gt; 1.6.2 & lt; / Edition & gt; & Lt; / Dependencies & gt; & Lt; Dependency & gt; & Lt; Group & gt; Org.apache.ws.commons.axiom & lt; / Group & gt; & Lt; ArtifactId & gt; Axiom-api & lt; / ArtifactId> & Lt; Version & gt; 1.2.14 & lt; / Edition & gt; & Lt; / Dependencies & gt; & Lt; Dependency & gt; & Lt; Group & gt; Org.apache.ws.commons.axiom & lt; / Group & gt; & Lt; ArtifactId & gt; Axiom-implant & lt; / ArtifactId> & Lt; Version & gt; 1.2.14 & lt; / Edition & gt; & Lt; / Dependencies & gt; & Lt; Dependency & gt; & Lt; Group & gt; Org.apache.ws.commons.schema & lt; / Group & gt; & Lt; ArtifactId & gt; XmlSchema & lt; / ArtifactId> & Lt; Version & gt; 1.3.2 & lt; / Edition & gt; & Lt; / Dependencies & gt; & Lt; Dependency & gt; & Lt; Group & gt; Org.apache.axis2 & lt; / Group & gt; & Lt; ArtifactId & gt; Axis2-Transport-local & lt; / ArtifactId> & Lt; Version & gt; 1.6.2 & lt; / Edition & gt; & Lt; / Dependencies & gt; & Lt; Dependency & gt; & Lt; Group & gt; Org.apache.axis2 & lt; / Group & gt; & Lt; ArtifactId & gt; Axis2-Transportation- http & lt; / ArtifactId> & Lt; Version & gt; 1.6.2 & lt; / Edition & gt; & Lt; / Dependencies & gt; & Lt; Dependency & gt; & Lt; Group & gt; Org.apache.neethi & lt; / Group & gt; & Lt; ArtifactId & gt; Neethi & lt; / ArtifactId> & Lt; Version & gt; 3.0.2 & lt; / Edition & gt; & Lt; / Dependencies & gt; & Lt; Dependency & gt; & Lt; Group & gt; Org.apache.geronimo.specs & lt; / Group & gt; & Lt; ArtifactId & gt; Geronimo-jta_1.1_spec & lt; / ArtifactId> & Lt; Version & gt; 1.1 & lt; / Edition & gt; & Lt; Scope & gt; Provided & lt; / Scope & gt; & Lt; / Dependencies & gt; In fact, the free online book "Maven: The For Referrals" shows your exact picture. Case in their section  
 
 compile  radius relational dependencies on Geronimo "Java EE Spec" libraries are These spec libraries only apply JavaEE standard so if you inspect the contents of (for example)  
  jar -tf geronimo-javamail_1.4_spec-1.7.1.jar   
 You will get (among other things).  
  javax / javax / mail / javax / mail / address Class javax / mail / authenticationFailedException.class javax / mail / Authenticator.class (etc.)   
 Therefore, there should not be any harm in the appointment of these Jeromeimo jars with your application, but If it really bothers you (or if you actually face a problem), you can leave the transient dependencies together at  & lt; Exclusions & gt;  Block:  
  & lt; Dependency & gt; & Lt; Group & gt; Org.apache.ws.commons.axiom & lt; / Group & gt; & Lt; ArtifactId & gt; Axiom-api & lt; / ArtifactId> & Lt; Version & gt; 1.2.14 & lt; / Edition & gt; & Lt; Exclusions & gt; & Lt; Exclusion & gt; & Lt; Group & gt; Org.apache.geronimo.specs & lt; / Group & gt; & Lt; ArtifactId & gt; Geronimo-activation_1.1_spec & lt; / ArtifactId> & Lt; / Exclusion & gt; & Lt; Exclusion & gt; & Lt; Group & gt; Org.apache.geronimo.specs & lt; / Group & gt; & Lt; ArtifactId & gt; Geronimo-javamail_1.4_spec & lt; / ArtifactId> & Lt; / Exclusion & gt; & Lt; / Exclusions & gt; & Lt; / Dependencies & gt;   
 If you ship your own spare jars, but you should not bother with the hassle of leaving the Garnimo Jar, unless you go on a real problem.  
 Alternatively, you can consider using it only if you know to make sure that your deployment is the container.