That is because the Maven build is set up so that the relevant JARs
are endorsed automatically when running the unit tests.
Andreas
On Tue, Apr 10, 2012 at 10:06, Stadelmann Josef
josef.stadelm...@axa-winterthur.ch wrote:
Thanks Sagara,
I am very happy about your response. Thanks
What I do
Thank you Andreas,
But I feel that this is a bit too much of automatic silent maven-automatism.
If I am targeting a particular end java platform, i.e. JDK 1.6.0_05 for OpenVMS
and I do not know which jar's maven has automatically endorsed to keep it's
unit test running, I am confident that
On Tue, Apr 10, 2012 at 9:26 PM, Stadelmann Josef
josef.stadelm...@axa-winterthur.ch wrote:
Thank you Andreas,
But I feel that this is a bit too much of automatic silent
maven-automatism.
If I am targeting a particular end java platform, i.e. JDK 1.6.0_05 for
OpenVMS
and I do not know
This is not a Axis2 issue instead JDK 1.6 related JAX-WS issue, JDK 6
shipped JAXB 2.0 and JAX-WS 2.0 as a part of JDK but Axis2 uses newer
versions of both artifacts. In your case @RequestWrapper#partName
introduced starting from JAX-WS 2.2 [1] and not available on previous
versions[2].
It is
[exec:exec]
Starting Server
Exception in thread main java.lang.NoSuchMethodError:
javax.xml.ws.RequestWrapper.partName()Ljava/lang/String;
at
org.apache.axis2.jaxws.description.builder.converter.JavaMethodsToMDCCon
verter.attachRequestWrapperAnnotation(JavaMethodsToMDCConverter.java:203
)
