[jira] Resolved: (RAMPART-157) Duplicate namespace declaration in SingedEncryptedElements assertion

["Nandana Mihindukulasooriya (JIRA)" <ji...@apache.org>]

     [ https://issues.apache.org/jira/browse/RAMPART-157?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Nandana Mihindukulasooriya resolved RAMPART-157.
------------------------------------------------

    Resolution: Fixed

Applied the patch. Thanks Stefan.

http://svn.apache.org/viewvc?view=rev&revision=653992

> Duplicate namespace declaration in SingedEncryptedElements assertion
> --------------------------------------------------------------------
>
>                 Key: RAMPART-157
>                 URL: https://issues.apache.org/jira/browse/RAMPART-157
>             Project: Rampart
>          Issue Type: Bug
>          Components: rampart-policy
>         Environment: any
>            Reporter: Stefan Vladov
>            Assignee: Ruchith Udayanga Fernando
>            Priority: Minor
>         Attachments: SignedEncryptedElements.patch
>
>   Original Estimate: 0.08h
>  Remaining Estimate: 0.08h
>
> The serialize method in org.apache.ws.secpolicy.model.SignedEncryptedElements causes duplicate namespace declaration in the assertion. The bug seems to be introduced as a result of the bug fix to Rampart issue 123. The problematic code is: 
>         // xmlns:sp=".."
>         writer.writeNamespace(prefix, namespaceURI);
>         if (writerPrefix == null) {
>             // xmlns:sp=".."
>             writer.writeNamespace(prefix, namespaceURI);
>         }
> Normally the writer prefix won't be null, however if the SignedEncryptedElements assertion is the first in the policy and no prior declarations of the security policy namespace exist, the writer prefix is null and the namespace is declared twice, resulting in an exception when parsed afterwards.

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.