[jira] Resolved: (AXIS2-4514) Axis1.5 NPE nested down to jdom with working Axis1.4 Rampart Configuration

["Andreas Veithen (JIRA)" <ji...@apache.org>]

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

Andreas Veithen resolved AXIS2-4514.
------------------------------------

    Resolution: Cannot Reproduce

Unable to reproduce. Tested based on policy sample 03 with Axis2 trunk and Rampart trunk.

- Using policy.xml from http://markmail.org/message/dkrp2uo5lle23t57 : throws error "An unsupported token was provided" -> not an Axiom issue.
- Using policy.xml and services.xml from http://markmail.org/message/3gtllxp5lbueflui : works perfectly.

If you still encounter the issue with Axis2 trunk and Rampart trunk, please provide detailed instructions on how to reproduce it.

> 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://markmail.org/message/gecvkhpt2k7cvwnh
> 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.