[
https://issues.apache.org/jira/browse/RAMPART-168?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12667213#action_12667213
]
Andrei Ivanov commented on RAMPART-168:
---------------------------------------
In this change(revision 657726) you also modified this:
- RampartUtil.insertSiblingAfter(rmd,
this.getInsertionLocation(), elem);
+ elem = RampartUtil.insertSiblingAfter(rmd,
this.getInsertionLocation(), elem);
however, the 1.4 release does not contain this change and I get a NPE because
of this.
What happened?
> 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.
