[JBoss JIRA] (DROOLS-569) Property reactivity prevents index update
by Michael Biarnes Kiefer (JIRA)
[ https://issues.jboss.org/browse/DROOLS-569?page=com.atlassian.jira.plugin... ]
Michael Biarnes Kiefer updated DROOLS-569:
------------------------------------------
Fix Version/s: 6.3.0.Beta1
(was: 6.2.0.Final)
> Property reactivity prevents index update
> -----------------------------------------
>
> Key: DROOLS-569
> URL: https://issues.jboss.org/browse/DROOLS-569
> Project: Drools
> Issue Type: Bug
> Reporter: Mario Fusco
> Assignee: Mario Fusco
> Labels: backport-to-6.0.x
> Fix For: 6.3.0.Beta1
>
>
> When a property is part of the pattern matching it can anyway be excluded from the property reactivity with a negative watch. Anyway if the property is also indexed this implies that when the fact is modified it skips not only the modification propagation (as requested) but also the update of the corresponding index causing an inconsistency.
--
This message was sent by Atlassian JIRA
(v6.3.11#6341)
9 years, 4 months
[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: 6.3.0.Beta1
(was: 6.2.0.Final)
> 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
> Affects Versions: 6.1.0.Beta2
> Reporter: Geoffrey De Smet
> Assignee: Michael Anstis
> Fix For: 6.3.0.Beta1
>
>
> 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
(v6.3.11#6341)
9 years, 4 months
[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: 6.3.0.Beta1
(was: 6.2.0.Final)
> "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: 6.3.0.Beta1
>
>
> 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
(v6.3.11#6341)
9 years, 4 months
[JBoss JIRA] (WFCORE-582) CLI: ability to load command handlers from the available in the model extensions
by Alexey Loubyansky (JIRA)
Alexey Loubyansky created WFCORE-582:
----------------------------------------
Summary: CLI: ability to load command handlers from the available in the model extensions
Key: WFCORE-582
URL: https://issues.jboss.org/browse/WFCORE-582
Project: WildFly Core
Issue Type: Enhancement
Components: CLI
Reporter: Alexey Loubyansky
Assignee: Alexey Loubyansky
At the moment, the CLI supports Java ServiceLoader mechanism to load command handlers from outside the CLI module during the initialization. Although, for that to work, an optional dependency on the module which is providing its commands has to be added to the CLI module.xml.
This enhancement is created to remove the requirement to modify the CLI module.xml to load external commands. Instead, the CLI could consult the list of available extensions and determine the list of modules to look for command handler in.
--
This message was sent by Atlassian JIRA
(v6.3.11#6341)
9 years, 4 months
[JBoss JIRA] (WFLY-2160) Allow Expression for datasource subsystem enabled property
by Brian Stansberry (JIRA)
[ https://issues.jboss.org/browse/WFLY-2160?page=com.atlassian.jira.plugin.... ]
Brian Stansberry commented on WFLY-2160:
----------------------------------------
Further, the fix reads the attribute value and then invokes the "enable" op, which will overwrite the value of the attribute with "true", losing the expression.
The WFLY-2833 fix (https://github.com/wildfly/wildfly/pull/7084) may address some of this; I'm not sure. It too has the problem of resolving expressions in Stage.MODEL though.
> Allow Expression for datasource subsystem enabled property
> ----------------------------------------------------------
>
> Key: WFLY-2160
> URL: https://issues.jboss.org/browse/WFLY-2160
> Project: WildFly
> Issue Type: Bug
> Components: Domain Management, JCA
> Affects Versions: 8.0.0.Alpha4
> Reporter: Steven Rose
> Assignee: Stefano Maestri
> Priority: Minor
> Labels: wildfly
> Fix For: 9.0.0.Beta1
>
>
> Currently the datasource sub system does not allow expressions. I would like to be able to do this: <datasource jta="true" jndi-name="java:/ds1DS" pool-name="ds1DS" enabled="${ds1.enabled}" use-java-context="true" use-ccm="true"> and set the ds1.enabled property via a properties file.
--
This message was sent by Atlassian JIRA
(v6.3.11#6341)
9 years, 4 months
[JBoss JIRA] (WFLY-2160) Allow Expression for datasource subsystem enabled property
by Brian Stansberry (JIRA)
[ https://issues.jboss.org/browse/WFLY-2160?page=com.atlassian.jira.plugin.... ]
Brian Stansberry reopened WFLY-2160:
------------------------------------
Assignee: Stefano Maestri (was: Jeff Zhang)
The fix in https://github.com/wildfly/wildfly/pull/6976 is not correct. It is resolving the expression in Stage.MODEL, which is too early.
Also, transformation is missing; see WFLY-4408.
> Allow Expression for datasource subsystem enabled property
> ----------------------------------------------------------
>
> Key: WFLY-2160
> URL: https://issues.jboss.org/browse/WFLY-2160
> Project: WildFly
> Issue Type: Bug
> Components: Domain Management, JCA
> Affects Versions: 8.0.0.Alpha4
> Reporter: Steven Rose
> Assignee: Stefano Maestri
> Priority: Minor
> Labels: wildfly
> Fix For: 9.0.0.Beta1
>
>
> Currently the datasource sub system does not allow expressions. I would like to be able to do this: <datasource jta="true" jndi-name="java:/ds1DS" pool-name="ds1DS" enabled="${ds1.enabled}" use-java-context="true" use-ccm="true"> and set the ds1.enabled property via a properties file.
--
This message was sent by Atlassian JIRA
(v6.3.11#6341)
9 years, 4 months