:30
To: axis-user@ws.apache.org
Subject: RE: Rampart 1.4 mustUnderstand
I switched back to axis 1.3 with rampart 1.3. Still getting
mustUnderstand=1. I see others with the issue when using their own
axis2.xml, but I'm using the default axis2.xml that comes with axis.
I
simply load
The Oasis 1.0 specification states:
All compliant implementations MUST declare which profiles they support and
MUST be able to
process a wsse:Security element including any sub-elements which may be
defined by that profile.
but it then says:
When a wsse:Security header includes a
2008 01:30
To: axis-user@ws.apache.org
Subject: RE: Rampart 1.4 mustUnderstand
I switched back to axis 1.3 with rampart 1.3. Still getting
mustUnderstand=1. I see others with the issue when using their own
axis2.xml, but I'm using the default axis2.xml that comes with axis. I
simply load
: 15 October 2008 01:30
To: axis-user@ws.apache.org
Subject: RE: Rampart 1.4 mustUnderstand
I switched back to axis 1.3 with rampart 1.3. Still getting
mustUnderstand=1. I see others with the issue when using their own
axis2.xml, but I'm using the default axis2.xml that comes with axis. I
In my case it still says mustUnderstand=1, but it tolerates the empty
header which 1.4 does not.
-Original Message-
From: RonnieMJ [mailto:[EMAIL PROTECTED]
Sent: 15 October 2008 01:30
To: axis-user@ws.apache.org
Subject: RE: Rampart 1.4 mustUnderstand
I switched back to axis 1.3
I switched back to axis 1.3 with rampart 1.3. Still getting
mustUnderstand=1. I see others with the issue when using their own
axis2.xml, but I'm using the default axis2.xml that comes with axis. I
simply load the client policy (attached). Is it something in my policy that
causes
Had the same issue recently, the security header coming back from the
service was empty in my case.
For now I'm using 1.3 until the issue I raised is resolved.
Try the same code with Axis 1.3 and Rampart 1.3 and see if that works
for you.
Taariq
-Original Message-
From: RonnieMJ
