[jboss-jira] [JBoss JIRA] (DROOLS-3923) (C)DI detection should be more reliable/standard for codegen

Edoardo Vacchi (Jira) issues at jboss.org
Mon Aug 5 04:19:02 EDT 2019


     [ https://issues.jboss.org/browse/DROOLS-3923?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Edoardo Vacchi updated DROOLS-3923:
-----------------------------------
    Sprint: 2019 Week 23-25, 2019 Week 26-28, 2019 Week 32-34  (was: 2019 Week 23-25, 2019 Week 26-28, 2019 Week 29-31)


> (C)DI detection should be more reliable/standard for codegen
> ------------------------------------------------------------
>
>                 Key: DROOLS-3923
>                 URL: https://issues.jboss.org/browse/DROOLS-3923
>             Project: Drools
>          Issue Type: Bug
>            Reporter: Edoardo Vacchi
>            Assignee: Edoardo Vacchi
>            Priority: Major
>              Labels: drools-core, submarine
>
> we are currently doing {{ try { Class.forName("...ApplicationScoped") } }} which is 
> (1) pretty hackish (2) won't work in Maven because maven's ClassPath is not the same of the target application
> We should rather use a config param or any better way to detect if we're going to use DI. Currently we have added a config param + "auto detect" using the technique above (in maven only the config param works) but auto-detect should be better.
> Besides ApplicationScoped only work for CDI, while JSR-330 @Inject is independent from CDI so using ApplicationScoped as a signal is too limited.



--
This message was sent by Atlassian Jira
(v7.12.1#712002)


More information about the jboss-jira mailing list