[WSS4J] dynamically configuring WSSConfig to work with previous WSS version 2003_06...

[Atul <te...@gmail.com>]

and it exceptions out (NullPointerException) in WSSReceiver at
        ((org.apache.axis.message.SOAPHeaderElement)
headerElement).setProcessed(true);

BUT, if I use the rebuilt wss4j after setting appropriate
compliance_mode (to OASIS_2003_06 in this case), And dynamically set
WSSConfig, then I guess it works. (BTW, the unit tests errors out with
this change).
Also, just rebuilding wss4j.jar doesn't help it either!

Do we need to rebuild the wss4j.jar and dynamically set properties in
WSSConfig to be able to get it to work with previous version?

Any pointers are really appreciated.

thx
atul.

Re: [WSS4J] dynamically configuring WSSConfig to work with previous WSS version 2003_06...

[Rami Jaamour <rj...@parasoft.com>]

Hello Atul,

It appearts that your email messages was chopped.

Rebuilding WSS4J is no longer needed for 2003 and 2002 messages in the 
latest WSS4J.  The javadocs in WSConstants are now outdated (I should 
submit a patch for this).  It should work only by adjusting the settings 
in the WSSConfig you pass to the API. AFAIK the compliance features were 
tested on the server side, they are only tested on clients, and 
specifically only the API is tested, not Axis deployments.  Have you 
tried making the settings to the default static instance of WSSConfig so 
it takes effect globally?  Also, setting the namespaces might not be 
sufficient, tweaking the other options might be necessary to interop 
with various previous WSS implementations.

Rami Jaamour
Software Engineer
SOAPtest Development
Parasoft Corporation

"We Make Software Work"


Atul wrote:

>and it exceptions out (NullPointerException) in WSSReceiver at
>        ((org.apache.axis.message.SOAPHeaderElement)
>headerElement).setProcessed(true);
>
>BUT, if I use the rebuilt wss4j after setting appropriate
>compliance_mode (to OASIS_2003_06 in this case), And dynamically set
>WSSConfig, then I guess it works. (BTW, the unit tests errors out with
>this change).
>Also, just rebuilding wss4j.jar doesn't help it either!
>
>Do we need to rebuild the wss4j.jar and dynamically set properties in
>WSSConfig to be able to get it to work with previous version?
>
>Any pointers are really appreciated.
>
>thx
>atul.
>
>  
>