November 2018 - jboss-jira - Jboss List Archives

[JBoss JIRA] (WFCORE-4205) unused optional dependencies in io and remoting

by Yeray Borges (Jira)

[ https://issues.jboss.org/browse/WFCORE-4205?page=com.atlassian.jira.plugi... ] Yeray Borges reassigned WFCORE-4205: ------------------------------------ Assignee: Yeray Borges > unused optional dependencies in io and remoting > ----------------------------------------------- > > Key: WFCORE-4205 > URL: https://issues.jboss.org/browse/WFCORE-4205 > Project: WildFly Core > Issue Type: Bug > Components: IO, Remoting > Reporter: Jean-Francois Denise > Assignee: Yeray Borges > Priority: Minor > > org.picketbox and org.jboss.as.security optional deps are not used in org.wildfly.extension.io and org.jboss.as.remoting -- This message was sent by Atlassian Jira (v7.12.1#712002)

7 years, 6 months

1
0
0 / 0

[JBoss JIRA] (WFCORE-4204) Add Phase priorities for MicroProfile DUPs

by Jeff Mesnil (Jira)

[ https://issues.jboss.org/browse/WFCORE-4204?page=com.atlassian.jira.plugi... ] Jeff Mesnil reassigned WFCORE-4204: ----------------------------------- Assignee: Jeff Mesnil (was: ehsavoie Hugonnet) > Add Phase priorities for MicroProfile DUPs > ------------------------------------------ > > Key: WFCORE-4204 > URL: https://issues.jboss.org/browse/WFCORE-4204 > Project: WildFly Core > Issue Type: Bug > Components: Server > Reporter: Jeff Mesnil > Assignee: Jeff Mesnil > Priority: Major > > New MicroProfile extensions were added late in the WildFly 14 release cycles and they did not properly define their priorities in org.jboss.as.server.deployment.Phase. > It introduce 5 new priorities: > {code} > public static final int DEPENDENCIES_MICROPROFILE_CONFIG = 0x1850; > public static final int DEPENDENCIES_MICROPROFILE_METRICS = 0x1860; > public static final int DEPENDENCIES_MICROPROFILE_HEALTH = 0x1870; > public static final int DEPENDENCIES_MICROPROFILE_OPENTRACING = 0x1880; > public static final int POST_MODULE_MICROPROFILE_CONFIG = 0x3750; > public static final int POST_MODULE_MICROPROFILE_METRICS = 0x3760; > public static final int POST_MODULE_MICROPROFILE_HEALTH = 0x3770; > public static final int POST_MODULE_MICROPROFILE_OPENTRACING = 0x3780; > {code} > Note that the metrics priorities correspond to a new extension (tracked by WFLY-10712) that's not in WildFly yet (but will be before 15.0 is released) -- This message was sent by Atlassian Jira (v7.12.1#712002)

7 years, 6 months

1
0
0 / 0

[JBoss JIRA] (WFCORE-4204) Add Phase priorities for MicroProfile DUPs

by Jeff Mesnil (Jira)

[ https://issues.jboss.org/browse/WFCORE-4204?page=com.atlassian.jira.plugi... ] Jeff Mesnil updated WFCORE-4204: -------------------------------- Component/s: Server (was: Deployment Scanner) > Add Phase priorities for MicroProfile DUPs > ------------------------------------------ > > Key: WFCORE-4204 > URL: https://issues.jboss.org/browse/WFCORE-4204 > Project: WildFly Core > Issue Type: Bug > Components: Server > Reporter: Jeff Mesnil > Assignee: ehsavoie Hugonnet > Priority: Major > > New MicroProfile extensions were added late in the WildFly 14 release cycles and they did not properly define their priorities in org.jboss.as.server.deployment.Phase. > It introduce 5 new priorities: > {code} > public static final int DEPENDENCIES_MICROPROFILE_CONFIG = 0x1850; > public static final int DEPENDENCIES_MICROPROFILE_METRICS = 0x1860; > public static final int DEPENDENCIES_MICROPROFILE_HEALTH = 0x1870; > public static final int DEPENDENCIES_MICROPROFILE_OPENTRACING = 0x1880; > public static final int POST_MODULE_MICROPROFILE_CONFIG = 0x3750; > public static final int POST_MODULE_MICROPROFILE_METRICS = 0x3760; > public static final int POST_MODULE_MICROPROFILE_HEALTH = 0x3770; > public static final int POST_MODULE_MICROPROFILE_OPENTRACING = 0x3780; > {code} > Note that the metrics priorities correspond to a new extension (tracked by WFLY-10712) that's not in WildFly yet (but will be before 15.0 is released) -- This message was sent by Atlassian Jira (v7.12.1#712002)

7 years, 6 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-3098) UX: Add support for map and list

by Daniele Zonca (Jira)

[ https://issues.jboss.org/browse/DROOLS-3098?page=com.atlassian.jira.plugi... ] Daniele Zonca commented on DROOLS-3098: --------------------------------------- [~uxdlc] Example: I have DO with this structure {code:java} PhoneNumber(String prefix, String number); Contact(String address, List[PhoneNumber] phoneNumbers); Agenda(Map[String, Contact] contacts) {code} I would like to create a column that is mapped to a phone number: Agenda.contacts["ContactName"].phoneNumbers[index].number I cannot do it now because I can only navigate through the tree element in the UI and I have no way to access into contacts *map* and the same which phone number in the *list* I want to use > UX: Add support for map and list > -------------------------------- > > Key: DROOLS-3098 > URL: https://issues.jboss.org/browse/DROOLS-3098 > Project: Drools > Issue Type: Story > Components: Scenario Simulation and Testing > Reporter: Daniele Zonca > Assignee: Liz Clayton > Priority: Major > Labels: ScenarioSimulation, UX, UXTeam > > As user I want to be able to use Data Objects that contain Lists and Maps -- This message was sent by Atlassian Jira (v7.12.1#712002)

7 years, 6 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-3283) Incorrect V&V results when operator is filled in the row (as opposed to column definition)

by Jozef Marko (Jira)

[ https://issues.jboss.org/browse/DROOLS-3283?page=com.atlassian.jira.plugi... ] Jozef Marko updated DROOLS-3283: -------------------------------- Affects Version/s: 7.14.0.Final > Incorrect V&V results when operator is filled in the row (as opposed to column definition) > ------------------------------------------------------------------------------------------ > > Key: DROOLS-3283 > URL: https://issues.jboss.org/browse/DROOLS-3283 > Project: Drools > Issue Type: Bug > Affects Versions: 7.14.0.Final > Reporter: Toni Rikkola > Assignee: Toni Rikkola > Priority: Major > Labels: drools-tools, support > > Imagine data model Person with attribute age. > If you create decision table and add two columns: > - both are defined against "age" attribute > - none of them have operator defined > then you add one row, and you fill in the operator and the value directly inside the row. > For example: > >= 20 > <= 30 > The generated DRL looks like this: > {code:java} > package org; > //from row number: 1 > rule "Row 1 AnotherTest" > dialect "mvel" > when > p : Person( age >= 20 , age <= 30 ) > then > p.setAgeGroup( "whatever" ); > end > {code} > The V&V will report this as conflicting row: > !6iOx.png|thumbnail! -- This message was sent by Atlassian Jira (v7.12.1#712002)

7 years, 6 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-3283) Incorrect V&V results when operator is filled in the row (as opposed to column definition)

by Jozef Marko (Jira)

[ https://issues.jboss.org/browse/DROOLS-3283?page=com.atlassian.jira.plugi... ] Jozef Marko updated DROOLS-3283: -------------------------------- Labels: drools-tools support (was: support) > Incorrect V&V results when operator is filled in the row (as opposed to column definition) > ------------------------------------------------------------------------------------------ > > Key: DROOLS-3283 > URL: https://issues.jboss.org/browse/DROOLS-3283 > Project: Drools > Issue Type: Bug > Affects Versions: 7.14.0.Final > Reporter: Toni Rikkola > Assignee: Toni Rikkola > Priority: Major > Labels: drools-tools, support > > Imagine data model Person with attribute age. > If you create decision table and add two columns: > - both are defined against "age" attribute > - none of them have operator defined > then you add one row, and you fill in the operator and the value directly inside the row. > For example: > >= 20 > <= 30 > The generated DRL looks like this: > {code:java} > package org; > //from row number: 1 > rule "Row 1 AnotherTest" > dialect "mvel" > when > p : Person( age >= 20 , age <= 30 ) > then > p.setAgeGroup( "whatever" ); > end > {code} > The V&V will report this as conflicting row: > !6iOx.png|thumbnail! -- This message was sent by Atlassian Jira (v7.12.1#712002)

7 years, 6 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-3282) Should not move to next AgendaGroup even if current is empty

by Edoardo Vacchi (Jira)

[ https://issues.jboss.org/browse/DROOLS-3282?page=com.atlassian.jira.plugi... ] Edoardo Vacchi updated DROOLS-3282: ----------------------------------- Description: Current implementation moves to next agend group if current agenda group is empty. This is unexpected, and in part detrimental in the impl of units: it is not possible to suspend execution of rules by switching to an empty group, because the engine will move to the next group anyway: {code} return nextRule != null && (!ruleAgendaItem.getAgendaGroup().equals( nextRule.getAgendaGroup() ) || !isHigherSalience(nextRule)); {code} because the change in behavior is potentially backwards incompatible we add a flag {{keepWhenEmpty}} that must be set to {{true}} when we want to enable this new behavior was: return nextRule != null && (!ruleAgendaItem.getAgendaGroup().equals( nextRule.getAgendaGroup() ) || !isHigherSalience(nextRule)); > Should not move to next AgendaGroup even if current is empty > ------------------------------------------------------------ > > Key: DROOLS-3282 > URL: https://issues.jboss.org/browse/DROOLS-3282 > Project: Drools > Issue Type: Bug > Reporter: Edoardo Vacchi > Assignee: Edoardo Vacchi > Priority: Major > Labels: drools-core > > Current implementation moves to next agend group if current agenda group is empty. This is unexpected, and in part detrimental in the impl of units: it is not possible to suspend execution of rules by switching to an empty group, because the engine will move to the next group anyway: > {code} > return nextRule != null && (!ruleAgendaItem.getAgendaGroup().equals( nextRule.getAgendaGroup() ) || !isHigherSalience(nextRule)); > {code} > because the change in behavior is potentially backwards incompatible we add a flag {{keepWhenEmpty}} that must be set to {{true}} when we want to enable this new behavior -- This message was sent by Atlassian Jira (v7.12.1#712002)

7 years, 6 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-3283) Incorrect V&V results when operator is filled in the row (as opposed to column definition)

by Jozef Marko (Jira)

[ https://issues.jboss.org/browse/DROOLS-3283?page=com.atlassian.jira.plugi... ] Jozef Marko updated DROOLS-3283: -------------------------------- Tester: Jozef Marko > Incorrect V&V results when operator is filled in the row (as opposed to column definition) > ------------------------------------------------------------------------------------------ > > Key: DROOLS-3283 > URL: https://issues.jboss.org/browse/DROOLS-3283 > Project: Drools > Issue Type: Bug > Reporter: Toni Rikkola > Assignee: Toni Rikkola > Priority: Major > Labels: support > > Imagine data model Person with attribute age. > If you create decision table and add two columns: > - both are defined against "age" attribute > - none of them have operator defined > then you add one row, and you fill in the operator and the value directly inside the row. > For example: > >= 20 > <= 30 > The generated DRL looks like this: > {code:java} > package org; > //from row number: 1 > rule "Row 1 AnotherTest" > dialect "mvel" > when > p : Person( age >= 20 , age <= 30 ) > then > p.setAgeGroup( "whatever" ); > end > {code} > The V&V will report this as conflicting row: > !6iOx.png|thumbnail! -- This message was sent by Atlassian Jira (v7.12.1#712002)

7 years, 6 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-3283) Incorrect V&V results when operator is filled in the row (as opposed to column definition)

by Toni Rikkola (Jira)

[ https://issues.jboss.org/browse/DROOLS-3283?page=com.atlassian.jira.plugi... ] Toni Rikkola commented on DROOLS-3283: -------------------------------------- [~jomarko] Should you be the QA on this one? > Incorrect V&V results when operator is filled in the row (as opposed to column definition) > ------------------------------------------------------------------------------------------ > > Key: DROOLS-3283 > URL: https://issues.jboss.org/browse/DROOLS-3283 > Project: Drools > Issue Type: Bug > Reporter: Toni Rikkola > Assignee: Toni Rikkola > Priority: Major > Labels: support > > Imagine data model Person with attribute age. > If you create decision table and add two columns: > - both are defined against "age" attribute > - none of them have operator defined > then you add one row, and you fill in the operator and the value directly inside the row. > For example: > >= 20 > <= 30 > The generated DRL looks like this: > {code:java} > package org; > //from row number: 1 > rule "Row 1 AnotherTest" > dialect "mvel" > when > p : Person( age >= 20 , age <= 30 ) > then > p.setAgeGroup( "whatever" ); > end > {code} > The V&V will report this as conflicting row: > !6iOx.png|thumbnail! -- This message was sent by Atlassian Jira (v7.12.1#712002)

7 years, 6 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-3283) Incorrect V&V results when operator is filled in the row (as opposed to column definition)

by Toni Rikkola (Jira)

[ https://issues.jboss.org/browse/DROOLS-3283?page=com.atlassian.jira.plugi... ] Toni Rikkola moved RHDM-786 to DROOLS-3283: ------------------------------------------- Project: Drools (was: Red Hat Decision Manager) Key: DROOLS-3283 (was: RHDM-786) Workflow: GIT Pull Request workflow (was: CDW with docs v1) Docs QE Status: NEW Affects Version/s: (was: 6.x.x) QE Status: NEW > Incorrect V&V results when operator is filled in the row (as opposed to column definition) > ------------------------------------------------------------------------------------------ > > Key: DROOLS-3283 > URL: https://issues.jboss.org/browse/DROOLS-3283 > Project: Drools > Issue Type: Bug > Reporter: Toni Rikkola > Assignee: Toni Rikkola > Priority: Major > Labels: support > > Imagine data model Person with attribute age. > If you create decision table and add two columns: > - both are defined against "age" attribute > - none of them have operator defined > then you add one row, and you fill in the operator and the value directly inside the row. > For example: > >= 20 > <= 30 > The generated DRL looks like this: > {code:java} > package org; > //from row number: 1 > rule "Row 1 AnotherTest" > dialect "mvel" > when > p : Person( age >= 20 , age <= 30 ) > then > p.setAgeGroup( "whatever" ); > end > {code} > The V&V will report this as conflicting row: > !6iOx.png|thumbnail! -- This message was sent by Atlassian Jira (v7.12.1#712002)

7 years, 6 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 November 2018