ws-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Daniel Kulp (JIRA)" <>
Subject [jira] [Created] (NEETHI-12) Problems if root element is not a policy element
Date Wed, 06 Jul 2011 16:17:17 GMT
Problems if root element is not a policy element

                 Key: NEETHI-12
             Project: Neethi
          Issue Type: Bug
    Affects Versions: 3.0
            Reporter: Daniel Kulp
            Assignee: Daniel Kulp
             Fix For: 3.0.1

If the root element passed to PolicyBuilder.getPolicy is not a wsp:Policy element, neethi
tries to parse/process it anyway.  Couple things happen:

1) If the element is a DOM or stream based, you get a Policy object with a bogus namespace.
 With the stream versions, the child iterator doesn't work correctly and only the first child
ends up returned;

2) With OM, if the element is not namespace qualified, you get a NPE.

We need to check to make sure we're getting a policy element and throw an exception otherwise.

This message is automatically generated by JIRA.
For more information on JIRA, see:


To unsubscribe, e-mail:
For additional commands, e-mail:

View raw message