OpenSAML user discussion

Further to this...

It seems that many validation-related things are failing because they use 
XMLObject.getOrderedChildren() to recurse down the object tree.

However, some of the implementation classes (e.g. AuthnContextImpl) have a 
getOrderedChildren() method that unconditionally adds elements to the 
children list even if the elements have not been set, leaving null entries in 
the list. Surely this is incorrect?

The effect is that in many places the code iterates through the children 
list, breaking with a NullPointerException when it attempts to dereference 
the null entry in the list. This makes it impossible to use, e.g., the 
inbuilt validation suites on objects that contain broken getOrderedChildren 
methods (unless all of the fields have been specified).


Chris