This metadata provider was added in v3.3.0.
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 use 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 adds XML files each containing a single
<md:EntityDescriptor> element to the
sourceDirectory. By default, when using the
sourceDirectory the file naming convention will be the lower case hex-encoded SHA-1 digest of the
entityID, suffixed with ".xml". Example: The metadata for the entity with
entityID "urn:test:foobar" will be resolved from the
sourceDirectory 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).
$ echo -n "urn:test:foobar" | openssl sha1 d278c9975472a6b4827b1a8723192b4e99aa969c
Any of the common attributes and dynamic attributes can be specified. In addition, the following attributes are available:
|Bean reference||Identifies the Spring bean for the |
|Bean reference||internal default instance||Identifies a Spring bean for a |
Convenience mechanism for wiring a
Any of the common child elements may be specified.