[ 
https://issues.apache.org/jira/browse/RAMPART-147?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12584458#action_12584458
 ] 

Miguel Arauzo commented on RAMPART-147:
---------------------------------------

Hi Nandana,
    I was referring to the official 1.3 release. I downloaded the last nightly 
build (from the 31st March) and saw that it had been corrected. But we are 
working in a production environment and need a stable release.

    Where can I find the list of supported features for the 1.3 release? I 
could find very little documentation on WS-Policy support in Rampart.

    And do you happen to know when the next stable release will be available?

Thanks

> Header parts included in EncryptedParts are not processed by Rampart
> --------------------------------------------------------------------
>
>                 Key: RAMPART-147
>                 URL: https://issues.apache.org/jira/browse/RAMPART-147
>             Project: Rampart
>          Issue Type: Bug
>          Components: rampart-policy
>    Affects Versions: 1.3
>            Reporter: Miguel Arauzo
>            Assignee: Ruchith Udayanga Fernando
>
> The method 'processElement' from class 
> org.apache.ws.secpolicy.builders.EncryptedPartsBuilder doesn't add the 
> 'sp:Header' elements to the SignedEncryptedParts instance:
> private void processElement(OMElement element, SignedEncryptedParts parent) {
>         
>         QName name = element.getQName();
>         
>         if (HEADER.equals(name)) {
>             Header header = new Header();
>             
>             OMAttribute nameAttribute = element.getAttribute(NAME);
>             if( nameAttribute != null ) {
>                 header.setName(nameAttribute.getAttributeValue());
>             }
>             
>             OMAttribute namespaceAttribute = element.getAttribute(NAMESPACE);
>             header.setNamespace(namespaceAttribute.getAttributeValue());
>             
>             <<== The following code is missing:     parent.addHeader(header);
>         } else if (BODY.equals(name)) {
>             parent.setBody(true);            
>         }        
>     }
> The result from this "missing line of code" is that it's impossible to 
> process a message that has some encrypted element besides the SOAP body.

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

Reply via email to