[JBoss JIRA] (DROOLS-3925) Refactor isReadOnly mechanism in Test Scenario
by Daniele Zonca (Jira)
Daniele Zonca created DROOLS-3925:
-------------------------------------
Summary: Refactor isReadOnly mechanism in Test Scenario
Key: DROOLS-3925
URL: https://issues.jboss.org/browse/DROOLS-3925
Project: Drools
Issue Type: Task
Components: Scenario Simulation and Testing
Reporter: Daniele Zonca
Assignee: Daniele Zonca
Refactor ScenarioSimulationEditorPresenter.cleanReadOnlyColumn and ScenarioGrid.isPropertyAssigned to use the same logic in a utils class
--
This message was sent by Atlassian Jira
(v7.12.1#712002)
7 years, 3 months
[JBoss JIRA] (DROOLS-3923) (C)DI detection should be more reliable/standard for codegen
by Edoardo Vacchi (Jira)
Edoardo Vacchi created DROOLS-3923:
--------------------------------------
Summary: (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
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)
7 years, 3 months