OpenSAML user discussion

[Neill Miller <>]

Hello Scott,

Thanks for the response.  I think I follow what you're saying, but can you 
provide an example of what the XML would look like in that case without the 
type?

Also, any ideas on what that would look like in code since it seems the type 
is present when building the object:

XSMyType myTypeValue = mtb.buildObject(
    AttributeValue.DEFAULT_ELEMENT_NAME, XSMyType.TYPE_NAME);

Should I be building the object differently without the type parameter?

thanks,
-Neill.

----- Original Message -----
From: "Scott Cantor" 
<>
To: 

Sent: Friday, February 6, 2009 12:06:08 PM GMT -06:00 US/Canada Central
Subject: RE: [OpenSAML] OpenSAML 2.0 custom data type help

Neill Miller wrote on 2009-02-06:
> That's likely because of the way the XMLHelper.appendTextContent is working.
> Is there another method I can use that won't cause the escaping, or is there
> a better XML output format I should be working toward to get this going?

Without commenting on the code, I will say you shouldn't use xsi:type at all 
if it's not a built-in type. The standard makes that quite clear. Schema 
typing is brittle, and largely broken in signature oriented use cases because 
QNames in content are so badly supported in XML.

The implication, unfortunately, is that libraries like OpenSAML have to 
expose your data using proxy/wildcard objects rather than typesafe ones, but 
that's the cost of interoperability.

You can build your data using custom objects, but they shouldn't emit 
xsi:type.

-- Scott