So in the latter case ,
>> > the
>> > security header is not flagged as process. This causes AxisEngine to
>> cough
>> > as there are must understand headers not processed.
>> > We will fix this issue [1], so this no longer be a problem.
>> >
5, 2008 at 12:21 PM, Taariq Levack
> > <[EMAIL PROTECTED]>wrote:
> >
> >> In my case it still says mustUnderstand=1, but it tolerates the empty
> >> header which 1.4 does not.
> >>
> >> -Original Message-
> >> From: RonnieMJ [mailto:[EMAI
tUnderstand=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
>>
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 with rampart 1.3. Still getting
> mustUnderstand=1. I see others with the issue when using their own
> axis2.xml, but I'm us
nfDir + "/clientSecurityPolicy.xml"));
> stub._getServiceClient().setOptions(options);
>
>
> stub._getServiceClient().engageModule("rampart");
>
>
> I also don't have access to or control over what is used on the servic
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 with
Rampart 1.3 and see if that works
> for you.
>
> Taariq
>
> -Original Message-
> From: RonnieMJ [mailto:[EMAIL PROTECTED]
> Sent: 10 October 2008 23:32
> To: axis-user@ws.apache.org
> Subject: Rampart 1.4 mustUnderstand
>
>
> Does rampart version 1.4 d
ailto:[EMAIL PROTECTED]
Sent: 10 October 2008 23:32
To: axis-user@ws.apache.org
Subject: Rampart 1.4 mustUnderstand
Does rampart version 1.4 default mustUnderstand to 1? I'm getting the
famous
error, and am using a policy to set my configurations in code (client
side
ONLY).
My wsse:securit
loadPolicy(confDir + "/clientSecurityPolicy.xml"));
stub._getServiceClient().setOptions(options);
stub._getServiceClient().engageModule("rampart");
I also don't have access to or control over what is used on the service side
(externa
