Skip to:

  1. Skip to Jira Navigation
  2. Skip to Side Navigation
  3. Skip to Main Content

Allow to instantiate a DefaultIdentifierGeneratorFactory which does not bind to the BeanManager

Description

introduced the ability for DefaultIdentifierGeneratorFactory to use managed beans as IdentifierGenerators; There currently is no way to opt-out from this, which should generally be fine as the BeanManager will simply not manage classes which aren't beans, but it's still useful to allow an SPI such as a custom `StandardServiceInitiator` to explicitly disable this new capability.

Activity

Nicolas HerzogMay 20, 2022 at 1:53 PM

Solution: Implement ServiceContributor (register it via Java ServiceLoader facility) and add a custom initiator (subclass) for MutableIdentifierGeneratorFactoryInitiator. That is, return a new DefaultIdentifierGeneratorFactory(true) within initiateService.

Fixed

Details

Assignee

Reporter

Components

Fix versions

Priority

Created July 27, 2021 at 3:45 PM
Updated May 20, 2022 at 1:53 PM
Resolved July 29, 2021 at 11:04 AM