Skip to Content.
Sympa Menu

mace-opensaml-users - Re: [OpenSAML] XACML providers not correctly registered by DefaultBootstrap?

Subject: OpenSAML user discussion

List archive

Re: [OpenSAML] XACML providers not correctly registered by DefaultBootstrap?


Chronological Thread 
  • From: Kenny Pearce <>
  • To:
  • Subject: Re: [OpenSAML] XACML providers not correctly registered by DefaultBootstrap?
  • Date: Tue, 29 Apr 2008 14:50:47 -0400
  • Organization: Hx Technologies

I've done some further research, and if you look at the
XACMLPolicyStatementImplBuilder source, it is setting the element and
type qnames to those for the ordinary <Statement> element, which is why
the factories can't find it. This is a bug, right?

On Tue, 2008-04-29 at 13:14 -0400, Kenny Pearce wrote:
> Hi,
> I am using the latest OpenSAML binary release (2.1.0) and trying to
> construct an XACMLPolicyStatement. The XMLObjectBuilderFactory cannot
> find a builder for it. If I manually instantiate an
> XACMLPolicyStatementTypeImplBuilder, then it crashes later on because it
> can't find the marshaller and tries to use the XSAnyMarshaller. I have
> double-checked that I have an OpenSAML jar version with the relevant XML
> files. The only thing I can think of is that it may have to do with my
> version of xmltooling - I have built that from the latest SVN because I
> need my XSDateTime patch. However, it doesn't seem that there is an
> xacml-integration branch on xmltooling or anything like that. Besides,
> it seems to me that as long as DefaultBootstrap is right it shouldn't
> matter. Any idea why this would not work? Could xmltooling be the
> problem?
> Thanks,
>




Archive powered by MHonArc 2.6.16.

Top of Page