1 files changed, 22 insertions, 0 deletions
diff --git a/eaaf_modules/eaaf_module_pvp2_core/src/main/java/at/gv/egiz/eaaf/modules/pvp2/api/metadata/IPvpAddableChainingMetadataProvider.java b/eaaf_modules/eaaf_module_pvp2_core/src/main/java/at/gv/egiz/eaaf/modules/pvp2/api/metadata/IPvpAddableChainingMetadataProvider.java
new file mode 100644
index 00000000..8e5eb715
--- /dev/null
+++ b/eaaf_modules/eaaf_module_pvp2_core/src/main/java/at/gv/egiz/eaaf/modules/pvp2/api/metadata/IPvpAddableChainingMetadataProvider.java
@@ -0,0 +1,22 @@
+package at.gv.egiz.eaaf.modules.pvp2.api.metadata;
+
+import javax.annotation.Nonnull;
+
+import at.gv.egiz.eaaf.core.api.IGarbageCollectorProcessing;
+
+import org.opensaml.saml.metadata.resolver.MetadataResolver;
+
+public interface IPvpAddableChainingMetadataProvider {
+
+  /**
+   * Manually add a metadata resolver into a chaining metadata provider.
+   * <br>
+   * <b>If the chaining metadata provider also implements
+   *     {@link IGarbageCollectorProcessing} manually added provider
+   *     can be removed by garbage-collector process. This behavior
+   *     depends on chaining metadata-provider implementation. </b>
+   *
+   * @param resolver Metadata provider that should be added
+   */
+  void addMetadataResolverIntoChain(@Nonnull MetadataResolver resolver);
+}