Uploaded image for project: 'CDI Specification Issues'
  1. CDI Specification Issues
  2. CDI-35

add support for 'optional' beans

    XMLWordPrintable

Details

    • Feature Request
    • Status: Closed (View Workflow)
    • Major
    • Resolution: Duplicate Issue
    • 1.0
    • None
    • None
    • Medium

    Description

      sometimes it's neat to mark a bean as @Optional depending if a specified class can get loaded or not.

      This is a simple way to implement deployment specific functionality.

      An example would be a BvalSupportBean which only should become active if the JSR-303 bean validation API can be found on the classpath.

      Attachments

        Issue Links

          Activity

            People

              pmuiratbleepbleep Pete Muir
              struberg Mark Struberg
              Votes:
              0 Vote for this issue
              Watchers:
              1 Start watching this issue

              Dates

                Created:
                Updated:
                Resolved: