OpenSAML user discussion

[Brent Putman <>]

Well, those XS* types are I believe all XML Schema simple types, like string, integer, etc.  Your type as you gave in your example is a complex type, that has child elements, etc.  That means your type isn't just going to have a single property/value like those do.  It will have possibly many properties (so getter/setter pairs) for the attributes and/or element content represented by your complex type.  Therefore looking at the XS* examples probably isn't very illustrative for what you would be doing.  Look at any of the other multitude of XMLObject impls that have attributes and/or child elements, but not those.

Note that you have 2 "things" in what you gave:  1) the custom type that you are trying to create as an AttributeValue element (which might also be representable as an element with a different name, but I don't know what your conceptual schema for that looks like) 2) the child element of that custom type.   Both have their own XML content model (where the second is a part of the first).  So you'd need 2 XMLObject providers, one for each.



Neill Miller wrote:

Hello Brent,

Ok, now I'm just confused.  I've been following the directions for creating a new SAML object at the link you pointed to and am already extending XMLObject (well, ValidatingXMLObject actually).  I've implemented the interface, the impl, the builder, the marshaller, the unmarshaller, and even have the stubs for the validator (but haven't really done much with it) -- all based on the XS* types included in the library.

My interface is defined as follows:

public interface XSMyType extends ValidatingXMLObject {

The impl is defined as follows:

public class XSMyTypeImpl extends AbstractValidatingXMLObject implements XSMyType {

So what is it exactly that my type is missing and needs to get this done?

thanks,
-Neill.

----- Original Message -----
From: "Brent Putman" 
To: "Neill Miller" , 
Sent: Monday, February 9, 2009 1:12:45 PM GMT -06:00 US/Canada Central
Subject: Re: [OpenSAML] OpenSAML 2.0 custom data type help



Neill Miller wrote:
  

Hello Brent,

Thanks!  Could you describe a little more about implementing the XMLObject providers for my custom type?  I'm new to the library and am not familiar with that terminology.  I realize treating the object as text isn't the way to go, but I'm having a hard time trying to get the type built any other way.  I'd like to try the first method you mentioned, but am not sure where to start.  Grepping the code, I see a lot of references to 'XMLObjectProvider*' in the test cases, but I'm not sure how that applies to this case.

  
    

An XMLObject is the fundamental interface in the OpenSAML stack. 
Generally, you have an XMLObject implementation for each XML element
and/or type that you want to support.  I'd suggest consulting the
developer's guide, if you haven't already.

https://spaces.internet2.edu/display/OpenSAML/OSTwoDeveloperManual


Mostly what you need to know is in the "Creating New Components"
section, in the "Creating a new SAML Object" +  Marshaller, Unmarshaller
sections.  Note that a SAMLObject is just a specialization in
java-opensaml2 of the base type XMLObject defined in java-xmltooling.