[
https://issues.apache.org/jira/browse/AXIS2-4514?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12794670#action_12794670
]
Andreas Veithen commented on AXIS2-4514:
----------------------------------------
The NPE is caused by the change in WSCOMMONS-337. On the other hand, calling
insertSiblingAfter only makes sense for nodes that have a parent. Some more
investigation is needed to check why Rampart attempts to use this method on a
node without parent.
> Axis1.5 NPE nested down to jdom with working Axis1.4 Rampart Configuration
> --------------------------------------------------------------------------
>
> Key: AXIS2-4514
> URL: https://issues.apache.org/jira/browse/AXIS2-4514
> Project: Axis2
> Issue Type: Bug
> Components: modules
> Affects Versions: 1.5
> Environment: Not a development specific issue.
> Reporter: Paul R
> Assignee: Andreas Veithen
>
> There is a very detailed description of the issue at this thread:
> http://mail-archives.apache.org/mod_mbox/ws-rampart-dev/200907.mbox/%[email protected]%3e
> I am not one of the two people in that thread but I am experiencing the issue
> and have tried to debug the issue by downloading Rampart v1.4 source code.
> It would appear that the NPE occurs when the Signed WS-S header is being
> added after the Username token has already been added.
> I traced the NPE down to RampartUtil:
> ((OMElement) child).insertSiblingAfter((OMElement) sibling);
> where neither child nor sibling is null so insertSiblingAfter has the NPE.
> The thread described above has example policy and configuration files. I had
> to downgrade to Axis2 v1.4 and everything started working again.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
