You are viewing a plain text version of this content. The canonical link for it is here.

Posted to rampart-dev@ws.apache.org by "Sumit Shah (JIRA)" <ji...@apache.org> on 2008/12/18 18:53:44 UTC

[jira] Updated: (RAMPART-207) Issue with SecureConversationToken.serialize()

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

Sumit Shah updated RAMPART-207:
-------------------------------

    Attachment: SecureConversationToken.java

The attachment contains the fix for the issue. Please review.

Sumit Shah

> Issue with SecureConversationToken.serialize()
> ----------------------------------------------
>
>                 Key: RAMPART-207
>                 URL: https://issues.apache.org/jira/browse/RAMPART-207
>             Project: Rampart
>          Issue Type: Bug
>          Components: rampart-policy
>    Affects Versions: 1.4
>            Reporter: Sumit Shah
>            Assignee: Ruchith Udayanga Fernando
>         Attachments: SecureConversationToken.java
>
>
> Issue with SecureConversationToken.serialize() method. 
> The org.apache.ws.secpolicy.model.SecureConversationToken.serialize() method: Line 102 appends the namespace twice to the inclusion parameter. The namespace is already appended in when initializing the 'inclusion' variable at line 96/98.
> I have attached the fix with this issue.
> Thanks
> Sumit Shah 

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