OpenSAML user discussion

[Brent Putman <>]

Scott Cantor wrote:
> Actually I thought there was one, so perhaps this is only a problem because
> of how the XACML classes were done...
>
>   


Good memory, in looking back at the code, the 
AbstractSAMLObjectUnmarshaller used to do just that:


   protected void processChildElement(XMLObject parentSAMLObject, 
XMLObject childSAMLObject)
           throws UnmarshallingException {
       if (Configuration.ignoreUnknownElements()) {
           if (log.isDebugEnabled()) {
               log.debug("Ignoring unknown element " + 
childSAMLObject.getElementQName());
           }
       } else {
           throw new 
UnmarshallingException(childSAMLObject.getElementQName()
                   + " is not an element supported by this unmarshaller");
       }
   }


Same for the attributes.


But Chad removed this in java-opensaml2 with r668 on 5/16/06.    In 
don't know why.