-
Bug
-
Resolution: Done
-
Major
-
8.0.0.CR1
-
None
I've configured a static module for PicketLink CDI library. This library provides some extensions which are loaded fine, as described by WFLY-1370.
However, I'm trying to deploy my application which the following producer method:
@Produces @PicketLink public PartitionManager getPartitionManager() { // produce an instance }
Where the @PicketLink annotation is a qualifier that allows my deployment to provide its own instance instead.
In the PicketLink side, we have a injection point as follows:
@Inject
@PicketLink
private Instance<PartitionManager> partitionManagerInstance;
Where a call to partitionManagerInstance.isUnsatisfied() always returns true, even if my deployment provides a proper producer method.
The issue here is that the producer method is never called, despite the use of qualifiers or not.
FYI, I'm able to listen for events fired by PicketLink during the application startup as follows:
public void observeIdentityConfigurationEvent(@Observes IdentityConfigurationEvent event) {
// observer
}
Where IdentityConfigurationEvent is one of the lifecycle events fired by PicketLink during the startup.
- blocks
-
WFLY-2733 Create PicketLink Federation and IDM extension and subsystems
-
- Closed
-
-
PLINK-319 WildFly PicketLink Extension and IDM Subsystem
-
- Resolved
-
- is blocked by
-
-
- Resolved
-
-
WFLY-2761 Make it possible for static cdi-enabled modules to see the beans in top-level deployments
-
- Closed
-
- is related to
-
-
- Closed
-
