-
Sub-task
-
Resolution: Fixed
-
L3 - Default
-
None
-
None
Problem
- Quarkus does not respect the content of a META-INF/beans.xml file. The following options can be configured in CDI 1.0:
- Interceptors
- Decorators
- Alternatives
- In Weld 1.1, it is additionally possible to configure the following options:
- Scan: include / exclude
- Weld documentation:
<scan> provides fine control over the classes loaded by Weld for scanning by nesting a number of include and exclude filters. [...]
- Weld documentation:
- Scan: include / exclude
Reasoning
- Interceptors (
CAM-13752), Alternatives (CAM-13747), and Decorators are automatically discovered and registered by Quarkus- Exclusion is possible via the property quarkus.arc.exclude-types in the application.properties file
- For Alternatives, there are even more ways to control them via Quarkus see
CAM-13747
- The Weld-specific scan configuration might be mightier compared with what can be configured in Quarkus
Decision
We should not try to provide Camunda-specific ways to replace the beans.xml file. Instead, we should document this limitation and make the users aware that there are alternative ways to configure Quarkus similarly (either programmatically or via application.properties file).
This is the controller panel for Smart Panels app
- is caused by
-
CAM-13562 Engine CDI module is integrated into Quarkus Extension
- Closed