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 "Nandana Mihindukulasooriya (JIRA)" <ji...@apache.org> on 2008/12/19 05:13:44 UTC

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

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

Nandana Mihindukulasooriya commented on RAMPART-207:
----------------------------------------------------

Hi Sumit,
       Once again, thanks for the patch. This is also fixed in the trunk. Issue is [1].

thanks,
nandana

[1] - http://issues.apache.org/jira/browse/RAMPART-170

> 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.


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

Posted by Sumit Shah <Su...@cgifederal.com>.
I did not take the trunk. I used the released version.

Thanks
Sumit

-----Original Message-----
From: Nandana Mihindukulasooriya (JIRA) [mailto:jira@apache.org] 
Sent: Thursday, December 18, 2008 11:14 PM
To: rampart-dev@ws.apache.org
Subject: [jira] Commented: (RAMPART-207) Issue with
SecureConversationToken.serialize()


    [
https://issues.apache.org/jira/browse/RAMPART-207?page=com.atlassian.jir
a.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=1265800
1#action_12658001 ] 

Nandana Mihindukulasooriya commented on RAMPART-207:
----------------------------------------------------

Hi Sumit,
       Once again, thanks for the patch. This is also fixed in the
trunk. Issue is [1].

thanks,
nandana

[1] - http://issues.apache.org/jira/browse/RAMPART-170

> 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.