OpenSAML user discussion

[Brent Putman <>]

Scott Cantor wrote:

Does this explanation help a bit more on what the problem is?
    

I know this much...if you want the XML content to be directly composed with the AttributeValue element, than you need to instantiate your XMLObject class with a builder call that overrides the element QName to be saml:AttributeValue.
  

Yes, exactly. I think somewhere in this long thread he alreadly illustrated this, but:  1) obtain the builder from the Configuration builder factory using the type QName, and then build using the AttributeValue element QName, using the builder method that omits explicit _expression_ of the xsi:type.

Anyway, if what you want is your element inside the <AttributeValue> element, then the piece you're missing is that you need to build the AttributeValue object first, and then add your object as a child element to it.
  

Right, and recognizing that in this case you need an XMLObject to use as the underlying implementation of the AttributeValue.  Like Scott suggested, instead of developing a custom type, you could theoretically just use the XSAny provider for the AttributeValue object, and just create a provider to represent your child element, adding that at runtime as a child of the XSAny.  If you're omitting the xsi:type on the AttributeValue, this is functionally going to result in the saml XML anyway.