Skip to content
GitLab
  • Menu
Projects Groups Snippets
  • /
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
    • Contribute to GitLab
  • Sign in
  • E eid-server
  • Project information
    • Project information
    • Activity
    • Labels
    • Members
  • Repository
    • Repository
    • Files
    • Commits
    • Branches
    • Tags
    • Contributors
    • Graph
    • Compare
  • Issues 0
    • Issues 0
    • List
    • Boards
    • Service Desk
    • Milestones
  • Merge requests 0
    • Merge requests 0
  • CI/CD
    • CI/CD
    • Pipelines
    • Jobs
    • Schedules
  • Deployments
    • Deployments
    • Environments
    • Releases
  • Monitor
    • Monitor
    • Metrics
    • Incidents
  • Analytics
    • Analytics
    • Value stream
    • CI/CD
    • Repository
  • Wiki
    • Wiki
  • Snippets
    • Snippets
  • Activity
  • Graph
  • Create a new issue
  • Jobs
  • Commits
  • Issue Boards
Collapse sidebar
  • ecsec Public
  • reqesidta-prototype
  • eid-server
  • Merge requests
  • !3

Veto managed bean using extension in favour of producing the config.

  • Review changes

  • Download
  • Email patches
  • Plain diff
Merged Neil Crossley requested to merge enable_config_injection into master Aug 06, 2019
  • Overview 0
  • Commits 2
  • Changes 3

This is a different solution than discussed, that works quite explicitly.

By using the CDI extensions, we can hook into the discovery process and veto the registration of the class SSAConfig as a managed bean.

https://www.next-presso.com/2017/02/nobody-expects-the-cdi-portable-extensions/#processannotatedtype-event

Inspiration here: https://stackoverflow.com/a/55990362

Assignee
Assign to
Reviewer
Request review from
Time tracking
Source branch: enable_config_injection