OpenSAML user discussion

[Chad La Joie <>]

The library will look for builders/marshallers/unmarshallers based on 
two things; the schema type (preferred) or the element QName.  So my 
guess is that the problem is one of two things:

- You haven't registered your objects with the library for the schema 
type you're implementing.

- The XML your unmarhsalling doesn't have the schema type declared on 
the Statement (which would be schema invalid XML) and so the library 
can't determine that it should use your classes.

Pedro Navarro Pérez wrote:
> I've already done all these classes, but the point is that is an 
> saml:Statement with a xsi:type, not an 
> xacml-saml:XACMLAuthzDecisionStatement, so when the PoolManager tries to 
> parse it, it tries to search the unrmarshaller for a saml:Statement, it 
> doesn't find it.
>
> Chad La Joie a écrit :
> > You need to implement an XMLObject for that particular type and then a 
> > builder, marshaller, and unmarshaller that builds, writes, and reads 
> > that object.  Then register those in the configuration file for OpenSAML.
> >
> > The OpenSAML documentation has fall out of sync but I'm going to work 
> > on cleaning it up today.  Once done you can refer to here for 
> > instructions on how to do this:
> >
> > https://spaces.internet2.edu/display/SHIB/OSTwoDeveloperManual
> >
> > Pedro Navarro Pérez wrote:
> > > Yes, you are right. But, when I tried to unmarshall an:
> > >
> > > <saml:Statement xsi:type=""xacml-saml:XACMLAuthzDecisionType"> I have 
> > > an error because there is neither UnMarshaller nor builder associated 
> > > by the DOM element Statement
> > >
> > > What do you recommend me to implement this?
> > >
> > > Thanks
> > >
> > > Chad La Joie a écrit :
> > > > There is nothing to code.  Statement is an abstract type without 
> > > > content, it's the equivalent to a marker interface in Java.
> > > >
> > > > Pedro Navarro Pérez wrote:
> > > > > Hi,
> > > > >
> > > > > I'm trying to extend the OpenSAML to implement the SAML 2.0 profile 
> > > > > of XACML 2.0, and when I try to construct an <saml:Statement 
> > > > > xsi:type"xacml-saml:XACMLAuthzDecisionType"> I realize that there 
> > > > > is no implementation (impl, builder, unmarshaller, marshaller) when 
> > > > > the standard points out:
> > > > >
> > > > > <complexType name="AssertionType">
> > > > >        <sequence>
> > > > >            <element ref="saml:Issuer"/>
> > > > >            <element ref="ds:Signature" minOccurs="0"/>
> > > > >            <element ref="saml:Subject" minOccurs="0"/>
> > > > >            <element ref="saml:Conditions" minOccurs="0"/>
> > > > >            <element ref="saml:Advice" minOccurs="0"/>
> > > > >            <choice minOccurs="0" maxOccurs="unbounded">
> > > > >                *<element ref="saml:Statement"/>*
> > > > >                <element ref="saml:AuthnStatement"/>
> > > > >                <element ref="saml:AuthzDecisionStatement"/>
> > > > >                <element ref="saml:AttributeStatement"/>
> > > > >            </choice>
> > > > > </sequence>
> > > > >
> > > > > So, Are you planning to code this Statement implementation.
> > > > >
> > > > > Thanks
> > > > >
> > > > > Pedro Navarro Pérez

--
Chad La Joie             2052-C Harris Bldg
OIS-Middleware           202.687.0124