Rampart breaks xml document in soap message when using policies
---------------------------------------------------------------
Key: RAMPART-128
URL: https://issues.apache.org/jira/browse/RAMPART-128
Project: Rampart
Issue Type: Bug
Components: rampart-core
Affects Versions: 1.3
Environment: windows xp sp2, tomcat 6 (on localhost), axis2 1.3,
rampart 1.3
Reporter: Fredrik Gustavsson
Priority: Minor
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?
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
