Skip to Content.
Sympa Menu

mace-opensaml-users - Re: [OpenSAML] unable to add ResourceContent (XML any type) to Resource attribute with opensaml.

Subject: OpenSAML user discussion

List archive

Re: [OpenSAML] unable to add ResourceContent (XML any type) to Resource attribute with opensaml.


Chronological Thread 
  • From: "Michael Lausch" <>
  • To:
  • Subject: Re: [OpenSAML] unable to add ResourceContent (XML any type) to Resource attribute with opensaml.
  • Date: Thu, 2 Oct 2008 10:21:27 +0200
  • Domainkey-signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=message-id:date:from:to:subject:in-reply-to:mime-version :content-type:content-transfer-encoding:content-disposition :references; b=PNpy5sWUwmVY8zqud7NKDxC+krTxWaytyN0OAt0Z0W+2ELTKK41C+UP3nNxJyhdOZT RlPeNk0jmWA1M9dDR3DBwFDyQ2RLAjFi+2b8NOY2fBtt9zVpkW6AZEedBeM3SCIsBEAo L2tXTRu1KXLmdiibMTqRsuViwc6HJgQKOjiUg=

On Wed, Oct 1, 2008 at 9:45 PM, Brent Putman
<>
wrote:
> Right, we don't have XMLObject model for SOAP 1.2 like Scott said. If
> you want a generic XMLObject that can be used to represent any arbitrary
> XML object model, you can use what we call the default provider, which
> is currently implemented by XSAny. Nominally this is used for things
> that are declared explicitly as xs:anyType, but since it can hold any
> content model (for the ur-type xs:anyType), it can be used for things
> for which you don't otherwise have an XMLObject implementation. The
> easiest way to get an unmarshaller for that is:
>
> unmarshallerFactory.getUnmarshaller(Configuration.getDefaultProviderQName());
>
>
> The XSAny instance you get when you unmarshall using that has the
> following API:
>
> http://www.opensaml.org/docs/xmltooling/1.0.1/apidocs/org/opensaml/xml/schema/XSAny.html
>
> As you can see, it is ElementExtensible- and AttributeExtensible- and
> also exposes the textContent, so that's how you gain access to the
> wrapped content model.

That did the trick. thx a lot for help.



Archive powered by MHonArc 2.6.16.

Top of Page