According to the CDI Reference#Limitations:
Portable Extensions are not supported
Therefore, it is not possible to use CDI libraries such as Apache DeltaSpike that utilise the javax.enterprise.inject.spi.Extension
mechanism.
Although this is documented (via #559), not implementing the CDI specification causes integration and migration headaches as it requires re-implementing via BeanRegistrarBuildItem
.
Is the eventual goal that ArC will cover the complete CDI specification?
Is the eventual goal that ArC will cover the complete CDI specification?
No, it's not a goal to implement all CDI features and pass the CDI TCK. CDI portable extensions are indeed very powerful yet they do not match the Quarkus "design philosophy" (build time metadata processing, reduction in reflection usage, etc.). We would like to provide the build time extension points for the most common tasks that are usually solved by CDI portable extensions.
This cherry-picking policy is causing more problems than it solves.
Closing as "won't fix" for now
Most helpful comment
This cherry-picking policy is causing more problems than it solves.