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/05/19 07:47:55 UTC
[jira] Commented: (RAMPART-168) When SecureConversationTokens are
used Rampart always try to use the attached reference
[ https://issues.apache.org/jira/browse/RAMPART-168?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12597875#action_12597875 ]
Nandana Mihindukulasooriya commented on RAMPART-168:
----------------------------------------------------
http://svn.apache.org/viewvc/webservices/rampart/trunk/java/modules/rampart-core/src/main/java/org/apache/rampart/builder/BindingBuilder.java?view=diff&r1=657725&r2=657726&pathrev=657726
> When SecureConversationTokens are used Rampart always try to use the attached reference
> ----------------------------------------------------------------------------------------
>
> Key: RAMPART-168
> URL: https://issues.apache.org/jira/browse/RAMPART-168
> Project: Rampart
> Issue Type: Bug
> Components: rampart-core
> Reporter: Nandana Mihindukulasooriya
> Assignee: Nandana Mihindukulasooriya
> Fix For: 1.4
>
>
> When SecureConversationTokens are used Rampart always try to use the attached reference when present even when the token is not included in the message.
> OMElement ref = tok.getAttachedReference();
> if(ref == null) {
> ref = tok.getUnattachedReference();
> }
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.