mace-opensaml-users - RE: [OpenSAML] XACML providers not correctly registered by DefaultBootstrap?
Subject: OpenSAML user discussion
List archive
- From: "Scott Cantor" <>
- To: <>
- Subject: RE: [OpenSAML] XACML providers not correctly registered by DefaultBootstrap?
- Date: Thu, 1 May 2008 16:43:33 -0400
- Organization: The Ohio State University
> Actually, in the rest of opensaml2, and in the xmltooling encryption and
> signature providers, all the unmarshallers and marshallers actually extend
a
> specific subclass of the appropriate abstract XMLObject ones, and the
> unmarshallers delegate to the super if they encounter an element/attribute
> they can't process. Some of those abstract supers just log it, some just
> ignore, but at least it's a point where we could do some kind of handling
if
> we so chose. Maybe we could have a flag on Configuration that determines
> whether unknowns are a fatal error or just logged, and then implement
there.
Yes, I do the same thing (handle it in a base class I mean) and I happen to
think throwing is the proper behavior, but if it's at least an option that
would be better.
Actually I thought there was one, so perhaps this is only a problem because
of how the XACML classes were done...
-- Scott
- Re: [OpenSAML] XACML providers not correctly registered by DefaultBootstrap?, Kenny Pearce, 05/01/2008
- Re: [OpenSAML] XACML providers not correctly registered by DefaultBootstrap?, Brent Putman, 05/01/2008
- <Possible follow-up(s)>
- Re: [OpenSAML] XACML providers not correctly registered by DefaultBootstrap?, Brent Putman, 05/01/2008
- RE: [OpenSAML] XACML providers not correctly registered by DefaultBootstrap?, Scott Cantor, 05/01/2008
- Message not available
- Re: [OpenSAML] XACML providers not correctly registered by DefaultBootstrap?, Brent Putman, 05/01/2008
- Re: [OpenSAML] XACML providers not correctly registered by DefaultBootstrap?, HÃ¥kon Sagehaug, 05/02/2008
Archive powered by MHonArc 2.6.16.