[RAMPART-128] Rampart breaks xml document in soap message when using policies

• Type: Bug
• Status: Open
• Priority: Minor
• Resolution: Unresolved
• Affects Version/s: 1.3
• Component/s: rampart-core
• Environment: windows xp sp2, tomcat 6 (on localhost), axis2 1.3, rampart 1.3
• Assignee: Unassigned
• Reporter: Fredrik Gustavsson
• Created: 19/Dec/07 09:13
• Updated: 22/Aug/10 21:35

Description

I'm using axis2 with rampart policy (signing and encrypting the soap message).
I noticed that if I have a web service that has a response xml that contains elements that are not name space prefixed, like in this example where elements "con" and "param" doesn't have a namespace declaration.

<?xml version="1.0" encoding="UTF-8"?>
<c:config xmlns:c="http://www.foo.com/foo/configuration">
<c:configurations>
<con name="theName" description="theDesc">
<param name="pName1" value="val1" />
<param name="pName2" value="val2" />
</con>
</c:configurations>
</c:config>

then the xml document will be corrupt on the client side after the security module (rampart) have been invoked.
The result is that all xml elements that miss the prefix are stripped of their parameters, e.g.

<?xml version="1.0" encoding="UTF-8"?>
<c:config xmlns:c="http://www.foo.com/foo/configuration">
<c:configurations>
<con>
<param />
<param />
</con>
</c:configurations>
</c:config>

This error doesn't occur when I'm not using policies.

My guess is that this has something todo with RampartEngine/RampartMessageData uses the Axiom doom when processing the message?

Issue Links

• is blocked by: RAMPART-303 Incorrect XML Passed to Digest Algorithm when XML Elements Belong to Empty Namespace
• is blocked by: AXIOM-97 org.apache.axiom.om.impl.dom.ElementImpl class's hasAttributes() and getAttributes() methods are not compatible with DOM interfaces.