Revisit deferred classnames for solving layering conflicts
Done
Description fields
Basics
Logistics
Basics
Logistics
Description
There are several places in the refactored metadata and attribute libraries that rely on IdP classes. The current workaround for this is to hardcode IdP classnames into various Spring parsers in those new libraries and instantiate the classes at runtime to use them in bean definition builders.
If we feel the need to improve this with a more robust solution, this is a summary of where the trick was used:
There are several places in the refactored metadata and attribute libraries that rely on IdP classes. The current workaround for this is to hardcode IdP classnames into various Spring parsers in those new libraries and instantiate the classes at runtime to use them in bean definition builders.
If we feel the need to improve this with a more robust solution, this is a summary of where the trick was used:
net.shibboleth.spring.metadata.filter.PredicateFilterParser
net.shibboleth.idp.attribute.resolver.spring.BaseResolverPluginParser
net.shibboleth.idp.attribute.resolver.spring.dc.impl.SubjectDataConnectorParser
net.shibboleth.idp.attribute.resolver.spring.ad.impl.SubjectDerivedAttributeDefinitionParser