Page tree
Skip to end of metadata
Go to start of metadata

You are viewing an old version of this page. View the current version.

Compare with Current View Page History

« Previous Version 2 Next »

The LocalDynamicMetadataProvider fetches metadata from a local source dynamically as needed.

The deployer is responsible for populating the local source with data, which may be done while the metadata provider is running.  New metadata will be seen automatically the first time it is requested after being added to the source. 

A common case will be to use a filesystem directory as the local source.  A convenience attribute sourceDirectory is supplied to facilitate this configuration.  In this case, the deployer would then add new XML files containing 1 EntityDescriptor each to this directory.  By default, when using sourceDirectory the naming convention will the the lower case hex-encoded digest of the descriptor's entityID, suffixed with ".xml".  Example: The metadata for the entity with entityID "urn:test:foobar" will be resolved from the source directory with filename "d278c9975472a6b4827b1a8723192b4e99aa969c.xml".

Note that with the default entityID digest mechanism, the digested value should not include any leading or trailing whitespace (i.e. no trailing new line character). 

Example generating default source key with OpenSSL
echo -n "urn:test:foobar" | openssl sha1

 

Attributes

Any of the common attributes and dynamic attributes can be specified. In addition, the following attributes are available:

AttributeTypeDefaultDescription
sourceManagerRefBean reference Identifies the Spring bean for the XMLObjectLoadSaveManager which serves as the local source of metadata.  Either this attribute or sourceDirectory is required.
sourceKeyGeneratorRefBean referenceinternal default instanceIdentifies a Spring bean for a Function which generates the string key used with the XMLObjectLoadSaveManager. The internal default implementation produces the lower-case hex-encoded SHA-1 digest of the entityID of the input criterion.  If the manager was effectively specified via sourceDirectory, then the internal default implementation suffixes this source key with ".xml".
sourceDirectoryFile specification 

Convenience mechanism for wiring a FilesystemLoadSaveManager, loading from the specified source directory in the local filesystem. This attribute will be ignored if sourceManagerRef is also specified.  Either this attribute or sourceManagerRef is required.

Child Elements

Any of the common child elements may be specified.

 

  • No labels