XdsObjects Help file
XdsObjects Namespace / XdsDomain Class / RepositoryAddresses Property
Example



In This Topic
    RepositoryAddresses Property
    In This Topic
    Holds the lookup table for mapping a Repository UniqueID to an EndPoint address
    Syntax
    Public Property RepositoryAddresses As Dictionary(Of String,WebServiceEndpoint)
    Dim instance As XdsDomain
    Dim value As Dictionary(Of String,WebServiceEndpoint)
     
    instance.RepositoryAddresses = value
     
    value = instance.RepositoryAddresses
    public Dictionary<string,WebServiceEndpoint> RepositoryAddresses {get; set;}
    Remarks

    One of the more difficult and badly defined areas of XDS.b is the requirement that systems directly accessing repositories (Document Consumers and Responding Gateways) must be able to translate from a Repository Unique ID to an endpoint address. This Dictionary provides that functionality. In most applications, this dictionary is loaded just once at application startup, from a configuration file, local web service etc., and its use is then transparent, as methods such as RetrieveDocumentSet then use it internally without further user/developer interaction.

    By using an WebServiceEndpoint object as the target, a domain may contain a mixture of secure and insecure endpoints, and may even use different client certificates for different connections.

    Example
    This example shows how to set up 2 different repositories - one to use secure and one to use insecure communications.
    XdsDomain Domain = new XdsDomain();
                X509Certificate2 Certificate = new X509Certificate2();
                //Load certificate from Store or file
                Domain.RepositoryAddresses.Add("1.2.840.99999.1.2.3", new XdsEndpoint("http://insecure/Retrieve");
                Domain.RepositoryAddresses.Add("1.2.840.99999.1.2.3.4", new XdsEndpoint("https://secure/Retrieve", Certificate));
    Requirements

    Target Platforms: Windows 7, Windows Vista SP1 or later, Windows XP SP3, Windows Server 2008 (Server Core not supported), Windows Server 2008 R2 (Server Core supported with SP1 or later), Windows Server 2003 SP2

    See Also