Uploaded image for project: 'WildFly'
  1. WildFly
  2. WFLY-2689

@Producer method never called when producing a bean from a static module

    XMLWordPrintable

Details

    • Bug
    • Resolution: Done
    • Major
    • 8.0.0.Final
    • 8.0.0.CR1
    • CDI / Weld
    • None
    • Hide

      1) Please clone this branch:

      https://github.com/pedroigor/picketlink-as-subsystem/tree/WFLY_8.PLINK-348

      2) Run mvn -Pintegration-tests clean install

      3) Start WildFly from the following location target/integration-tests/containers/wildfly-8.0.0.CR1/

      4) Run the following Arquillian test: test.org.picketlink.as.subsystem.core.integration.AuthenticationWithSubsystemPartitionManagerTestCase

      The test.org.picketlink.as.subsystem.core.integration.MyPartitionManagerProducer producer method is never called.

      Show
      1) Please clone this branch: https://github.com/pedroigor/picketlink-as-subsystem/tree/WFLY_8.PLINK-348 2) Run mvn -Pintegration-tests clean install 3) Start WildFly from the following location target/integration-tests/containers/wildfly-8.0.0.CR1/ 4) Run the following Arquillian test: test.org.picketlink.as.subsystem.core.integration.AuthenticationWithSubsystemPartitionManagerTestCase The test.org.picketlink.as.subsystem.core.integration.MyPartitionManagerProducer producer method is never called.

    Description

      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.

      Attachments

        Issue Links

          blocks

          Feature Request - Feature requests from customers and/or users WFLY-2733 Create PicketLink Federation and IDM extension and subsystems

          • Major - To be worked after higher priority work items are addressed. When the severity is high and the effort to change it is low to moderate, this term is chosen. Issues in this category likely have an existing workaround but implementation or execution may be non-trivial.
          • Closed

          Task - Represents a small unit of work that is not end-user facing. PLINK-319 WildFly PicketLink Extension and IDM Subsystem

          • Major - To be worked after higher priority work items are addressed. When the severity is high and the effort to change it is low to moderate, this term is chosen. Issues in this category likely have an existing workaround but implementation or execution may be non-trivial.
          • Resolved
          is blocked by

          Task - Represents a small unit of work that is not end-user facing. WELD-1536 Cross-BDA resolution should not be transitive

          • Major - To be worked after higher priority work items are addressed. When the severity is high and the effort to change it is low to moderate, this term is chosen. Issues in this category likely have an existing workaround but implementation or execution may be non-trivial.
          • Resolved

          Enhancement - An enhancement to or refactoring of existing functionality that is not configurable by an end user (typically a change made by an internal team that affects users) WFLY-2761 Make it possible for static cdi-enabled modules to see the beans in top-level deployments

          • Blocker - To be worked above all other priorities. This term is chosen when the severity of the issue is very high, has no workaround, or the effort for the change is comparatively low. Issues that may be very publicly visible and could generate significant media attention may also drive a higher priority.
          • Closed
          is related to

          Feature Request - Feature requests from customers and/or users WFLY-1370 Add ability to load CDI portable extensions from static modules

          • Major - To be worked after higher priority work items are addressed. When the severity is high and the effort to change it is low to moderate, this term is chosen. Issues in this category likely have an existing workaround but implementation or execution may be non-trivial.
          • Closed

          Activity

            People

              rhn-engineering-jharting Jozef Hartinger
              psilva@redhat.com Pedro Igor Craveiro
              Votes:
              1 Vote for this issue
              Watchers:
              5 Start watching this issue

              Dates

                Created:
                Updated:
                Resolved: