November 2016 - jboss-jira - Jboss List Archives

[JBoss JIRA] (DROOLS-680) "contains" operator behaves inconsistently when used with Maps

by Michael Biarnes Kiefer (JIRA)

[ https://issues.jboss.org/browse/DROOLS-680?page=com.atlassian.jira.plugin... ] Michael Biarnes Kiefer updated DROOLS-680: ------------------------------------------ Fix Version/s: 7.0.0.Beta4 (was: 7.0.0.Beta3) > "contains" operator behaves inconsistently when used with Maps > -------------------------------------------------------------- > > Key: DROOLS-680 > URL: https://issues.jboss.org/browse/DROOLS-680 > Project: Drools > Issue Type: Bug > Affects Versions: 5.6.0.Final, 6.0.1.Final, 6.1.0.Final, 6.2.0.CR4 > Reporter: Davide Sottara > Assignee: Mario Fusco > Fix For: 7.0.0.Beta4 > > > In a rule > {code} > Bean( map contains "x" ) // assuming "map" is a property of type Map > {code} > "contains" is arbitrarily interpreted as "containsKey" > The constrain will then fail after being jitted > The documentation explicitly states that "contains" applies to collections -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years, 5 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-669) Create "behavesAs" operator to support traiting

by Michael Biarnes Kiefer (JIRA)

[ https://issues.jboss.org/browse/DROOLS-669?page=com.atlassian.jira.plugin... ] Michael Biarnes Kiefer updated DROOLS-669: ------------------------------------------ Fix Version/s: 7.0.0.Beta4 (was: 7.0.0.Beta3) > Create "behavesAs" operator to support traiting > ----------------------------------------------- > > Key: DROOLS-669 > URL: https://issues.jboss.org/browse/DROOLS-669 > Project: Drools > Issue Type: Feature Request > Affects Versions: 6.2.0.CR3 > Reporter: Davide Sottara > Assignee: Davide Sottara > Fix For: 7.0.0.Beta4 > > > Define an operator that would check if an object can provide *natively* all the methods required by an interface. This would ensure that, upon donning the interface as a trait, no soft field would be required, and that all methods in the interface would have a concrete implementation. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years, 5 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-670) Generalize inline casts to work with traits

by Michael Biarnes Kiefer (JIRA)

[ https://issues.jboss.org/browse/DROOLS-670?page=com.atlassian.jira.plugin... ] Michael Biarnes Kiefer updated DROOLS-670: ------------------------------------------ Fix Version/s: 7.0.0.Beta4 (was: 7.0.0.Beta3) > Generalize inline casts to work with traits > ------------------------------------------- > > Key: DROOLS-670 > URL: https://issues.jboss.org/browse/DROOLS-670 > Project: Drools > Issue Type: Enhancement > Affects Versions: 6.2.0.CR3 > Reporter: Davide Sottara > Assignee: Davide Sottara > Fix For: 7.0.0.Beta4 > > > The following constraint > {code} > Person( this#Worker( wage > 1000 ) ) > {code} > is admissible when Worker is a subtype of Person. > It should also be possible to use "#" when Worker is a donned trait. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years, 5 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-607) Match.getObjects() should reflect the patterns' order

by Michael Biarnes Kiefer (JIRA)

[ https://issues.jboss.org/browse/DROOLS-607?page=com.atlassian.jira.plugin... ] Michael Biarnes Kiefer updated DROOLS-607: ------------------------------------------ Fix Version/s: 7.0.0.Beta4 (was: 7.0.0.Beta3) > Match.getObjects() should reflect the patterns' order > ----------------------------------------------------- > > Key: DROOLS-607 > URL: https://issues.jboss.org/browse/DROOLS-607 > Project: Drools > Issue Type: Enhancement > Affects Versions: 5.5.0.Final, 5.6.0.Final, 6.0.0.Final, 6.1.0.Final > Reporter: Davide Sottara > Assignee: Mark Proctor > Priority: Minor > Fix For: 7.0.0.Beta4 > > > if Match.getObjects() is called on a rule with LHS A() B() C(), > the resulting list will have the matching objects in reversed order > - that is, [c, b, a] - making it more difficult to analyze it. > The object's position in the list should reflect the LHS. > The order should be preserved even when subnetworks are present. > For example, A() not B() C() should then result in the list [a, *, c ] -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years, 5 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-470) Decision Table (XLS) should support fixed conditions, such as SeatDesignation(isNeighborOf($guest))

by Michael Biarnes Kiefer (JIRA)

[ https://issues.jboss.org/browse/DROOLS-470?page=com.atlassian.jira.plugin... ] Michael Biarnes Kiefer updated DROOLS-470: ------------------------------------------ Fix Version/s: 7.0.0.Beta4 (was: 7.0.0.Beta3) > Decision Table (XLS) should support fixed conditions, such as SeatDesignation(isNeighborOf($guest)) > --------------------------------------------------------------------------------------------------- > > Key: DROOLS-470 > URL: https://issues.jboss.org/browse/DROOLS-470 > Project: Drools > Issue Type: Enhancement > Components: decision tables > Affects Versions: 6.1.0.Beta2 > Reporter: Geoffrey De Smet > Assignee: Michael Anstis > Labels: optaplanner-request-for-drools > Fix For: 7.0.0.Beta4 > > > This DT should work: > ||CONDITION||CONDITION||ACTION| > |$guest : SeatDesignation()|$neighbor : SeatDesignation(isNeighborOf($guest))|| > |guestName == "$param"|guestName == "$param"|doSomething();| > It crashes because of the "SeatDesignation(isNeighborOf($guest))". Only empty parenthesis are allowed. > Failing workaround 1: This workaround (as specified by the docs), does NOT work well, because it adds the same condition (isNeighborOf($guest)) multiple times in the same rule: > ||CONDITION||CONDITION||CONDITION||ACTION| > |$guest : SeatDesignation()|$neighbor : SeatDesignation()||| > |guestName == "$param"|isNeighborOf($guest), guestName == "$param"|isNeighborOf($guest), guestAge == "$param"|doSomething();| > Failing workaround 2: Adding an extra, hidden column with that condition does not work when new rows are added because condition columns with an empty cell are ignored. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years, 5 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-542) Expose more Commands through the KieCommands API

by Michael Biarnes Kiefer (JIRA)

[ https://issues.jboss.org/browse/DROOLS-542?page=com.atlassian.jira.plugin... ] Michael Biarnes Kiefer updated DROOLS-542: ------------------------------------------ Fix Version/s: 7.0.0.Beta4 (was: 7.0.0.Beta3) > Expose more Commands through the KieCommands API > ------------------------------------------------ > > Key: DROOLS-542 > URL: https://issues.jboss.org/browse/DROOLS-542 > Project: Drools > Issue Type: Feature Request > Affects Versions: 6.1.0.CR1 > Reporter: Davide Sottara > Assignee: Davide Sottara > Fix For: 7.0.0.Beta4 > > > Not all Commands are exposed by the KieCommands API interface -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years, 5 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-453) Allow KieSession globals configurable via kmodule.xml

by Michael Biarnes Kiefer (JIRA)

[ https://issues.jboss.org/browse/DROOLS-453?page=com.atlassian.jira.plugin... ] Michael Biarnes Kiefer updated DROOLS-453: ------------------------------------------ Fix Version/s: 7.0.0.Beta4 (was: 7.0.0.Beta3) > Allow KieSession globals configurable via kmodule.xml > ----------------------------------------------------- > > Key: DROOLS-453 > URL: https://issues.jboss.org/browse/DROOLS-453 > Project: Drools > Issue Type: Enhancement > Affects Versions: 6.0.0.Final > Reporter: Anton Giertli > Assignee: Mark Proctor > Fix For: 7.0.0.Beta4 > > > Looking at the current xsd of kmodule.xml > https://github.com/droolsjbpm/droolsjbpm-knowledge/blob/6.0.x/kie-api/src... > It is not possible to configure KieSession globals variables via kmodule.xml. > Given the fact it is already possible to configure almost every KieSession related features like listeners, handlers, loggers, globals, also session related, should be configurable through the kmodule.xml too. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years, 5 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-817) Extremely poor performance of the topological sorting implementation for type declarations performs

by Michael Biarnes Kiefer (JIRA)

[ https://issues.jboss.org/browse/DROOLS-817?page=com.atlassian.jira.plugin... ] Michael Biarnes Kiefer updated DROOLS-817: ------------------------------------------ Fix Version/s: 7.0.0.Beta4 (was: 7.0.0.Beta3) > Extremely poor performance of the topological sorting implementation for type declarations performs > ---------------------------------------------------------------------------------------------------- > > Key: DROOLS-817 > URL: https://issues.jboss.org/browse/DROOLS-817 > Project: Drools > Issue Type: Enhancement > Components: core engine > Affects Versions: 6.0.0.Final, 6.0.1.Final, 6.1.0.Final, 6.2.0.Final, 6.3.0.Beta1 > Reporter: Davide Sottara > Assignee: Davide Sottara > Priority: Minor > Fix For: 7.0.0.Beta4 > > > The current implementation suffers from thrashing. > In case of large business object models (e.g. derived from an ontology), > the analysis at package build time may take orders of magnitude more > than necessary -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years, 5 months

1
0
0 / 0

[JBoss JIRA] (WFLY-7081) Elytron + https-listener in undertow listener doesn't work with enable-http2 set to "true"

by Ingo Weiss (JIRA)

[ https://issues.jboss.org/browse/WFLY-7081?page=com.atlassian.jira.plugin.... ] Ingo Weiss commented on WFLY-7081: ---------------------------------- After some investigation, it seems that the issue happens when the HTTPS listener uses a {{ssl-context}}. Reverting to a security realm, HTTP/2 works as expected. > Elytron + https-listener in undertow listener doesn't work with enable-http2 set to "true" > ------------------------------------------------------------------------------------------ > > Key: WFLY-7081 > URL: https://issues.jboss.org/browse/WFLY-7081 > Project: WildFly > Issue Type: Bug > Components: Security > Reporter: Hynek Švábek > Assignee: Stuart Douglas > Priority: Blocker > Fix For: 11.0.0.Alpha1 > > > When I want to use HTTPS settings in combination with Elytron subsystem then I have to set "enable-http2" to "false" value. > For settings I followed this blog post http://darranl.blogspot.cz/2016/02/wildfly-elytron-ssl-configuration.html > And as keystore I used default application.keystore -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years, 5 months

1
0
0 / 0

[JBoss JIRA] (WFLY-7081) Elytron + https-listener in undertow listener doesn't work with enable-http2 set to "true"

by Stuart Douglas (JIRA)

[ https://issues.jboss.org/browse/WFLY-7081?page=com.atlassian.jira.plugin.... ] Stuart Douglas reassigned WFLY-7081: ------------------------------------ Assignee: Stuart Douglas (was: Darran Lofthouse) > Elytron + https-listener in undertow listener doesn't work with enable-http2 set to "true" > ------------------------------------------------------------------------------------------ > > Key: WFLY-7081 > URL: https://issues.jboss.org/browse/WFLY-7081 > Project: WildFly > Issue Type: Bug > Components: Security > Reporter: Hynek Švábek > Assignee: Stuart Douglas > Priority: Blocker > Fix For: 11.0.0.Alpha1 > > > When I want to use HTTPS settings in combination with Elytron subsystem then I have to set "enable-http2" to "false" value. > For settings I followed this blog post http://darranl.blogspot.cz/2016/02/wildfly-elytron-ssl-configuration.html > And as keystore I used default application.keystore -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years, 5 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 2016