[JBoss JIRA] (WFLY-12255) WFLY does not accept the Narayana's long version of property expiryScannerClassNames to define expiry scanners
by Ondrej Chaloupka (Jira)
Ondrej Chaloupka created WFLY-12255:
---------------------------------------
Summary: WFLY does not accept the Narayana's long version of property expiryScannerClassNames to define expiry scanners
Key: WFLY-12255
URL: https://issues.jboss.org/browse/WFLY-12255
Project: WildFly
Issue Type: Bug
Components: Transactions
Reporter: Ondrej Chaloupka
Assignee: Ondrej Chaloupka
The WFLY-951enables the way to set the Narayana settings of the expiry class names via system property. The issue enforces users to use only property in form {{RecoveryEnvironmentBean.expiryScannerClassNames}}. But Narayana provides to use either this shortened version of the property for any configuration option. But it accepts the longer form for property with fully qualified bean class name (https://jbossts.blogspot.com/2018/01/narayana-periodic-recovery-of-xa.htm...). In this case it's {{com.arjuna.ats.arjuna.common.RecoveryEnvironmentBean.expiryScannerClassNames}}. That property (which sets the same thing as its shortened version) should be accepted by the WFLY as well.
--
This message was sent by Atlassian Jira
(v7.12.1#712002)
6 years, 5 months
[JBoss JIRA] (DROOLS-4269) kogito-codegen-tests: alternative testing strategy for codegen
by Edoardo Vacchi (Jira)
Edoardo Vacchi created DROOLS-4269:
--------------------------------------
Summary: kogito-codegen-tests: alternative testing strategy for codegen
Key: DROOLS-4269
URL: https://issues.jboss.org/browse/DROOLS-4269
Project: Drools
Issue Type: Bug
Reporter: Edoardo Vacchi
Assignee: Edoardo Vacchi
Currently we are doing dynamic compilation and classloading to test code generation. I am proposing an alternative strategy that use the plain Maven plugin.
- create `kogito-codegen-tests`
- write data/rules/process sources under src/main/{java,resources}
- write tests under src/test/
tests are now allowed to refer directly to codegenerated classes by name.
just use mvn compile test to run the tests
caveat: not sure if the maven plugin is picked up from the current source tree or from the SNAPSHOT on the nexus, we need to check this
--
This message was sent by Atlassian Jira
(v7.12.1#712002)
6 years, 5 months
[JBoss JIRA] (DROOLS-4268) FIX XStream configuration
by Gabriele Cardosi (Jira)
Gabriele Cardosi created DROOLS-4268:
----------------------------------------
Summary: FIX XStream configuration
Key: DROOLS-4268
URL: https://issues.jboss.org/browse/DROOLS-4268
Project: Drools
Issue Type: Task
Components: Scenario Simulation and Testing
Reporter: Gabriele Cardosi
Assignee: Gabriele Cardosi
Fix XStream defaults to have a generated xml as "plain" as possible (remove "reference" use, remove "class" attribute for list elements)
--
This message was sent by Atlassian Jira
(v7.12.1#712002)
6 years, 5 months
[JBoss JIRA] (DROOLS-4216) Create runtime and testing version of kogito webapp
by Gabriele Cardosi (Jira)
[ https://issues.jboss.org/browse/DROOLS-4216?page=com.atlassian.jira.plugi... ]
Gabriele Cardosi resolved DROOLS-4216.
--------------------------------------
Resolution: Done
> Create runtime and testing version of kogito webapp
> ---------------------------------------------------
>
> Key: DROOLS-4216
> URL: https://issues.jboss.org/browse/DROOLS-4216
> Project: Drools
> Issue Type: Sub-task
> Components: Scenario Simulation and Testing
> Reporter: Gabriele Cardosi
> Assignee: Gabriele Cardosi
> Priority: Major
> Labels: ScenarioSimulation
>
> For each asset there should be two *kogito* webapp:
> # a **development/testing** one, that should provide **VS CODE** features,
> # a **runtime** one, without the above, to be used inside **VS CODE**
> To allow *inheritance* and avoid code-duplication, a common, parent *jar* will also be implemented
--
This message was sent by Atlassian Jira
(v7.12.1#712002)
6 years, 5 months