-
Feature Request
-
Resolution: Duplicate
-
Major
-
None
-
1.0
-
None
-
Medium
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.
- duplicates
-
CDI-50 Ability to veto beans, both unconditionally and based on classes visible
- Closed