public final class ParentExtensionStorage
Support for Containers with 'hierarchic BeanManagers'
This is mostly useful for EAR applications.
Some EE Container scan the common shared EAR lib path and reuse this information
for the webapps in the EAR. This is actually the only approach a container can
do to prevent mem leaks and side effects spreading to different webapps.
Of course this also means that the webapps get their own (different)
instances of an Extension.
To acknowledge this solution we provide a mechanism to lookup 'parent Extensions'
which is very similar to handling parent ClassLoaders.
Please note that you need to enable this handling if you are running DeltaSpike
in an EAR on a container which supports parent Extensions.
You can do that by settting "deltaspike.parent.extension.enabled" to "e;true"e;
All your Extension has to do is to register itself in
Later at boot time the Extension can lookup it's parent Extension instance and
e.g. check which classes got scanned in the parent ClassLoader.
The ExtensionInfo automatically gets removed if the webapp gets undeployed.