There are actually two things:
1. Neethi 2 (which is used in Axis2 1.5.x and 1.6.0) is much more
lenient and parses certain invalid policies without throwing an
exception. Neethi 3 (which is used starting with Axis2 1.6.1) no
longer accepts those policies and triggers the exception that you are
se
Jaime,
I got the latest axis2-1.7.0 and rampart snapshot using maven, and I found
that my client actually succeeds in adding the UsernameToken security
policy, which it fails to do in 1.6.1 (for me at least). I see axis2-1.7.0
uses neethi 3.0.2, and axis2-1.6.1 uses 3.0.1. I don't know if that
a
Also look at axis2.xml;
some axis2.xml delivered with jax-ws examples show various directories under
WEB-INF/
expected i.e. in cases when a pojo is to be deployed.
Such directories are not created by the axis2.war deployment process; So you
are on your own;
Deploying a jar with a web
On Thu, Apr 12, 2012 at 1:38 PM, Emmanuel GUITON <
emmanuel.gui...@intrinsec.com> wrote:
> Hello,
>
> ** **
>
> Indeed, I followed the guide you mentioned.
>
> But then, from what you say, the documentation may not be correct. See the
> following extract :
>
> ** **
>
> Packaging and
Hello,
Indeed, I followed the guide you mentioned.
But then, from what you say, the documentation may not be correct. See the
following extract :
Packaging and deploying a JAX-WS service
Axis2 provides two mechanisms for deploying JAX-WS services:
1.The service may be packaged and deployed a
