Re: [higgins-dev] Changes to STS

[Michael McIntosh <mikemci@xxxxxxxxxx>]

Alex,

My current implementation (not yet checked in) is, for a 
@xsi:type="xyz:map" the Java representation would be the Java 1.4 equiv of 
java.util.Map<String, Object>. For the following example:

<Setting Name="SAMLIssue" Type="xyz:map">
        <Setting Name="IncludeBearerSubjectName" Type="xs:boolean">true</
Setting>
        <Setting Name="TrustedDelegator" Type="xs:string">
mikemci@xxxxxxxxxx</Setting>
        <Setting Name="DefaultContextRef" Type="xs:anyURI">
file:///C:/higgins.config.xml?id=Higgins-LDAP-Server</Setting>
        <Setting Name="TokenIssuer" Type="xs:anyURI">
https://localhost/TokenService/services/Trust</Setting>
        <Setting Name="EncryptToken" Type="xs:boolean">false</Setting>
        <Setting Name="SubjectNameIdentifierAttribute" Type="xs:anyURI">
http://schemas.xmlsoap.org/ws/2005/05/identity/claims/emailaddress</
Setting>
        <Setting Name="SubjectNameIdentifierFormat" Type="xs:anyURI">
urn:oasis:names:tc:SAML:1.1:nameid-format:emailAddress</Setting>
</Setting>

There would be a java.util.Map representing the Setting with 
@Name="SAMLIssue" with entries representing each child Setting element.
The entries would be keyed by the values of the @Name attributes and the 
values would be Objects representing the values, typed according to the 
@xsi:type.

Thanks,
Mike

higgins-dev-bounces@xxxxxxxxxxx wrote on 03/27/2007 05:32:10 PM:

> 
> What is othe proposed XML Schema representation for Iterator?  The 
> link below has a table for XML Schema representation for all the 
> basic types but not collections or Iterator. 
> 
> Alex 
> 
> ***********************************************************************
> Alex Amies
> aamies@xxxxxxxxxx
> Tivoli Identity Manager
> http://www-306.ibm.com/software/tivoli/products/identity-mgr/
> 714 438 5085
> *********************************************************************** 
> 

> 
> "Jim Sermersheim" <jimse@xxxxxxxxxx> 
> Sent by: higgins-dev-bounces@xxxxxxxxxxx 
> 03/27/2007 09:54 AM 
> 
> Please respond to
> "Higgins \(Trust Framework\) Project developer discussions" 
> <higgins-dev@xxxxxxxxxxx>
> 
> To
> 
> <higgins-dev@xxxxxxxxxxx> 
> 
> cc
> 
> Subject
> 
> Re: [higgins-dev] Changes to STS
> 
> 
> 
> 
> <snip> 
> >As we discussed a long while ago (2nd f2f?), the current thinking is 
along 
> >the lines of:
> >        <Setting Name="..." xsi:type="...">...</Setting>
> >where the xsi:type indicates the format (in XML Schema terms of the 
> >content of the Setting element. Each unique xsi:type will map to a 
> >specific Java class for instance "xs:string" to java.lang.String and 
> >"xs:anyURI" to java.net.URI. For each xsi:type a handler will be 
> >registered to convert the content of the Setting element into an 
instance 
> >of the appropriate Java class:
> >        <SettingHandler Type="xs:string" Class="java.lang.String" 
> >Handler="... .StringHandler"/>. 
> I was planning to implement something that will build an IdAS 
> IProperty given an xsi type (like xs:string) and a lexical string. 
> The table of XML types to Java types being here http://www.eclipse.
> org/higgins/org.eclipse.higgins.
> docs/idas/org/eclipse/higgins/idas/ISimpleValue.html#getData(). 
> 
> I could also do the same for complex types (parsing the "value" will
> require an XML or DOM parser).  This code would probably end up in 
> org.eclipse.higgins.idas.cp.toolkit.BasicAttribute or 
> BasicSimpleAttribute and BasicComplexAttribute. 
> 
> If this is useful for other components, I wonder if we should put it
> somewhere else. 
> 
> <snip> 
> 
> Jim_______________________________________________
> higgins-dev mailing list
> higgins-dev@xxxxxxxxxxx
> https://dev.eclipse.org/mailman/listinfo/higgins-dev
> _______________________________________________
> higgins-dev mailing list
> higgins-dev@xxxxxxxxxxx
> https://dev.eclipse.org/mailman/listinfo/higgins-dev