August 2020 - jboss-jira - Jboss List Archives

[JBoss JIRA] (DROOLS-5588) Review kie-dmn-core questionmarkunarytest DMN examples version in codebase

by Matteo Mortari (Jira)

[ https://issues.redhat.com/browse/DROOLS-5588?page=com.atlassian.jira.plug... ] Matteo Mortari updated DROOLS-5588: ----------------------------------- Sprint: 2020 Week 31-33 (from Jul 27), 2020 Week 34-36 (from Aug 17) (was: 2020 Week 31-33 (from Jul 27)) > Review kie-dmn-core questionmarkunarytest DMN examples version in codebase > -------------------------------------------------------------------------- > > Key: DROOLS-5588 > URL: https://issues.redhat.com/browse/DROOLS-5588 > Project: Drools > Issue Type: Task > Components: dmn engine > Reporter: Matteo Mortari > Assignee: Matteo Mortari > Priority: Major > Fix For: 7.42.0.Final > > > see Epic descr -- This message was sent by Atlassian Jira (v7.13.8#713008)

5 years, 11 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-5588) Review kie-dmn-core questionmarkunarytest DMN examples version in codebase

by Matteo Mortari (Jira)

Matteo Mortari created DROOLS-5588: -------------------------------------- Summary: Review kie-dmn-core questionmarkunarytest DMN examples version in codebase Key: DROOLS-5588 URL: https://issues.redhat.com/browse/DROOLS-5588 Project: Drools Issue Type: Task Components: dmn engine Reporter: Matteo Mortari Assignee: Matteo Mortari Fix For: 7.42.0.Final see Epic descr -- This message was sent by Atlassian Jira (v7.13.8#713008)

5 years, 11 months

1
0
0 / 0

[JBoss JIRA] (WFLY-13778) Upgrade ironjacamar to 1.4.23.Final

by Tomasz Adamski (Jira)

[ https://issues.redhat.com/browse/WFLY-13778?page=com.atlassian.jira.plugi... ] Tomasz Adamski commented on WFLY-13778: --------------------------------------- Hi [~brian.stansberry], I have added the diff and removed EAP7 link. > Upgrade ironjacamar to 1.4.23.Final > ----------------------------------- > > Key: WFLY-13778 > URL: https://issues.redhat.com/browse/WFLY-13778 > Project: WildFly > Issue Type: Component Upgrade > Reporter: Tomasz Adamski > Assignee: Tomasz Adamski > Priority: Major > > [https://github.com/ironjacamar/ironjacamar/compare/ironjacamar-1.4.22.Fin...] -- This message was sent by Atlassian Jira (v7.13.8#713008)

5 years, 11 months

1
0
0 / 0

[JBoss JIRA] (WFLY-13778) Upgrade ironjacamar to 1.4.23.Final

by Tomasz Adamski (Jira)

[ https://issues.redhat.com/browse/WFLY-13778?page=com.atlassian.jira.plugi... ] Tomasz Adamski updated WFLY-13778: ---------------------------------- Description: [https://github.com/ironjacamar/ironjacamar/compare/ironjacamar-1.4.22.Fin...] > Upgrade ironjacamar to 1.4.23.Final > ----------------------------------- > > Key: WFLY-13778 > URL: https://issues.redhat.com/browse/WFLY-13778 > Project: WildFly > Issue Type: Component Upgrade > Reporter: Tomasz Adamski > Assignee: Tomasz Adamski > Priority: Major > > [https://github.com/ironjacamar/ironjacamar/compare/ironjacamar-1.4.22.Fin...] -- This message was sent by Atlassian Jira (v7.13.8#713008)

5 years, 11 months

1
0
0 / 0

[JBoss JIRA] (WFLY-13784) Add a Galleon layer for JBoss Diagnostic Reporting

by Yeray Borges Santana (Jira)

Yeray Borges Santana created WFLY-13784: ------------------------------------------- Summary: Add a Galleon layer for JBoss Diagnostic Reporting Key: WFLY-13784 URL: https://issues.redhat.com/browse/WFLY-13784 Project: WildFly Issue Type: Feature Request Components: Build System, JDR Reporter: Yeray Borges Santana Assignee: Yeray Borges Santana Create a Galleon layer to provision JDR subsystem -- This message was sent by Atlassian Jira (v7.13.8#713008)

5 years, 11 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-5587) SceSim requires an F5 and full Build when testing and importing DMN model

by Matteo Mortari (Jira)

Matteo Mortari created DROOLS-5587: -------------------------------------- Summary: SceSim requires an F5 and full Build when testing and importing DMN model Key: DROOLS-5587 URL: https://issues.redhat.com/browse/DROOLS-5587 Project: Drools Issue Type: Bug Components: Test Scenarios Editor Reporter: Matteo Mortari Assignee: Toni Rikkola Attachments: Screenshot 2020-08-20 at 09.39.37.png Create in BC 2 DMN files, when creating the importing model Save but don't build. Create SceSim for the importing model. Execution works but pop-up if failed values won't show actual values. !Screenshot 2020-08-20 at 09.39.37.png|thumbnail! (on mouseover no pop, clicking view alerts nothing happens) -- This message was sent by Atlassian Jira (v7.13.8#713008)

5 years, 11 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-5577) Calling static Java method from DMN model (Drools Business Central)

by Jozef Marko (Jira)

[ https://issues.redhat.com/browse/DROOLS-5577?page=com.atlassian.jira.plug... ] Jozef Marko updated DROOLS-5577: -------------------------------- Labels: support (was: ) > Calling static Java method from DMN model (Drools Business Central) > ------------------------------------------------------------------- > > Key: DROOLS-5577 > URL: https://issues.redhat.com/browse/DROOLS-5577 > Project: Drools > Issue Type: Bug > Components: DMN Editor, dmn engine > Affects Versions: 7.40.0.Final > Reporter: Kristina Mandekic > Assignee: Guilherme Gomes > Priority: Major > Labels: support > Attachments: Artifacts.PNG, Artifacts0.PNG, DroolsNewTypes5-0.0.1-SNAPSHOT.jar, dependencies.PNG, stdev 0.PNG, stdev 1.PNG > > > When calling static Java method {{stdev_a}} (which I created in a new Java Maven project) from Drools Business Central DMN project/model, I'm getting following error: > > {code:java} > DMN: Error compiling Java function 'stdev' on node 'stdev': Error resolving external function as defined by: function(val) external { java: { class: ""com.samplea.drools.DroolsNewTypes5.StandardDeviationA"", method signature: ""stdev_a(java.lang.Number)"" }} (DMN id: _3B4B6CBE-847B-4488-8754-214F506BBB48, Error compiling the referenced FEEL expression){code} > > Also, how to view logs of DMN model when it has build errors? -- This message was sent by Atlassian Jira (v7.13.8#713008)

5 years, 11 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-5577) Calling static Java method from DMN model (Drools Business Central)

by Jozef Marko (Jira)

[ https://issues.redhat.com/browse/DROOLS-5577?page=com.atlassian.jira.plug... ] Jozef Marko updated DROOLS-5577: -------------------------------- Tester: Jozef Marko > Calling static Java method from DMN model (Drools Business Central) > ------------------------------------------------------------------- > > Key: DROOLS-5577 > URL: https://issues.redhat.com/browse/DROOLS-5577 > Project: Drools > Issue Type: Bug > Components: DMN Editor, dmn engine > Affects Versions: 7.40.0.Final > Reporter: Kristina Mandekic > Assignee: Guilherme Gomes > Priority: Major > Attachments: Artifacts.PNG, Artifacts0.PNG, DroolsNewTypes5-0.0.1-SNAPSHOT.jar, dependencies.PNG, stdev 0.PNG, stdev 1.PNG > > > When calling static Java method {{stdev_a}} (which I created in a new Java Maven project) from Drools Business Central DMN project/model, I'm getting following error: > > {code:java} > DMN: Error compiling Java function 'stdev' on node 'stdev': Error resolving external function as defined by: function(val) external { java: { class: ""com.samplea.drools.DroolsNewTypes5.StandardDeviationA"", method signature: ""stdev_a(java.lang.Number)"" }} (DMN id: _3B4B6CBE-847B-4488-8754-214F506BBB48, Error compiling the referenced FEEL expression){code} > > Also, how to view logs of DMN model when it has build errors? -- This message was sent by Atlassian Jira (v7.13.8#713008)

5 years, 11 months

1
0
0 / 0

[JBoss JIRA] (WFLY-13783) Upgrade to WildFly Core 13.0.0.Beta5

by James Perkins (Jira)

[ https://issues.redhat.com/browse/WFLY-13783?page=com.atlassian.jira.plugi... ] James Perkins updated WFLY-13783: --------------------------------- Description: Dev tag: https://github.com/wildfly/wildfly-core/releases/tag/13.0.0.Beta5 Diff to previous integrated release: https://github.com/wildfly/wildfly-core/compare/13.0.0.Beta4...13.0.0.Beta5 [Release notes|https://issues.redhat.com/secure/ConfigureReport.jspa?versions=1234...] was: Dev tag: https://github.com/wildfly/wildfly-core/releases/tag/13.0.0.Beta5 Diff to previous integrated release: https://github.com/wildfly/wildfly-core/compare/13.0.0.Beta4...13.0.0.Beta5 > Upgrade to WildFly Core 13.0.0.Beta5 > ------------------------------------ > > Key: WFLY-13783 > URL: https://issues.redhat.com/browse/WFLY-13783 > Project: WildFly > Issue Type: Component Upgrade > Components: Management > Reporter: James Perkins > Assignee: James Perkins > Priority: Major > Fix For: 21.0.0.Beta1 > > > Dev tag: https://github.com/wildfly/wildfly-core/releases/tag/13.0.0.Beta5 > Diff to previous integrated release: https://github.com/wildfly/wildfly-core/compare/13.0.0.Beta4...13.0.0.Beta5 > [Release notes|https://issues.redhat.com/secure/ConfigureReport.jspa?versions=1234...] -- This message was sent by Atlassian Jira (v7.13.8#713008)

5 years, 11 months

1
0
0 / 0

[JBoss JIRA] (WFLY-13770) Create jdbc job repository using deployment descriptors

by Cheng Fang (Jira)

[ https://issues.redhat.com/browse/WFLY-13770?page=com.atlassian.jira.plugi... ] Cheng Fang edited comment on WFLY-13770 at 8/19/20 8:29 PM: ------------------------------------------------------------ Looks like this doc section is out of date. It should use the latest schema namespace ({{urn:jboss:domain:batch-jberet:2.0}}), and use {{data-source}} attribute when defining a jdbc job repository: {code:xml} <jboss xmlns="urn:jboss:1.0"> <batch xmlns="urn:jboss:domain:batch-jberet:2.0"> <job-repository> <jdbc data-source="ExampleDS"/> </job-repository> </batch> </jboss> {code} Besides the doc, batch subsystem and tests also need to be updated to support this use case. was (Author: cfang): Looks like this doc section is out of date. It should use the latest schema namespace ({{urn:jboss:domain:batch-jberet:2.0}}), and use {{data-source}} attribute when defining a jdbc job repository: {code:xml} <jboss xmlns="urn:jboss:1.0"> <batch xmlns="urn:jboss:domain:batch-jberet:2.0"> <job-repository> <jdbc data-source="java:jboss/datasources/ExampleDS"/> </job-repository> </batch> </jboss> {code} Besides the doc, batch subsystem and tests also need to be updated to support this use case. > Create jdbc job repository using deployment descriptors > ------------------------------------------------------- > > Key: WFLY-13770 > URL: https://issues.redhat.com/browse/WFLY-13770 > Project: WildFly > Issue Type: Enhancement > Components: Batch > Affects Versions: 20.0.1.Final > Reporter: Jurij Bernhardt > Assignee: Cheng Fang > Priority: Major > > The Example for "new Job Repository" ([https://docs.wildfly.org/20/Admin_Guide.html#deployment-descriptors]) doesn't work properly. > {code:xml} > <jboss xmlns="urn:jboss:1.0"> > <batch xmlns="urn:jboss:batch-jberet:1.0"> > <job-repository> > <jdbc jndi-name="java:jboss/datasources/ExampleDS"/> > </job-repository> > </batch> > </jboss> > {code} > Schema batch-jberet_1_0.xsd alllows only in-memory or named job-repositoryType. > You get the validation exception by using the jdbc example. > It would be useful to improve the batch-jberet integration so that the example given above would work. -- This message was sent by Atlassian Jira (v7.13.8#713008)

5 years, 11 months

1
0
0 / 0

2026

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

jboss-jira August 2020