axis-java-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Andreas Veithen <>
Subject Re: Removal of direct Axiom factory references in Rampart causes test failures when using xmlsec 1.5.2 or greater
Date Fri, 11 Jul 2014 12:31:50 GMT
That's a bug in Axiom. It still exists in the current trunk.


On Thu, Jul 10, 2014 at 11:29 PM,  <> wrote:
> Hi Rampart devs,
>   As you might already know wss4j 1.6.16 is out and while I was giving it a
> try with Rampart 1.7 snapshot, I encountered some test failures. One of
> these is a NPE in
> org.apache.rahas.impl.util.CommonUtilTest.testGetDecryptedBytes, which seem
> to be caused by recent changes in Rampart TestUtil that remove usage of
> Axiom DOOMAbstractFactory when constructing a SOAP envelope:
> It seems that with the new approach, the created SOAP envelope document does
> not have a "factory" field set, which causes NPE when doing a deep clone of
> an element created with that document instance.
> Deep cloning for KeyInfo elements was introduced in xmlsec 1.5.2:
> I prepared a sample test case that isolates the issue (attached). Also, I'm
> attaching a Rampart patch that can be used to reproduce this - it switches
> to wss4j 1.6.15 and stable Axiom, and applies a workaround for another issue
> in wss4j that was discovered recently.
> I would like to get some opinion on how to address this. Do you think that
> Rampart test utilities can be changed somehow to workaround this? If not,
> then this is probably an Axiom or XML Security's defect?
> Thanks,
>    Detelin
> ---------------------------------------------------------------------
> To unsubscribe, e-mail:
> For additional commands, e-mail:

To unsubscribe, e-mail:
For additional commands, e-mail:

View raw message