[JBoss JIRA] (DROOLS-88) Support generics in declared types' fields
by Michael Biarnes Kiefer (JIRA)
[ https://issues.jboss.org/browse/DROOLS-88?page=com.atlassian.jira.plugin.... ]
Michael Biarnes Kiefer updated DROOLS-88:
-----------------------------------------
Fix Version/s: 6.1.0.Beta4
(was: 6.1.0.Beta3)
> Support generics in declared types' fields
> ------------------------------------------
>
> Key: DROOLS-88
> URL: https://issues.jboss.org/browse/DROOLS-88
> Project: Drools
> Issue Type: Enhancement
> Security Level: Public(Everyone can see)
> Affects Versions: 5.5.0.Final
> Reporter: Davide Sottara
> Assignee: Davide Sottara
> Priority: Minor
> Fix For: 5.5.1.Final, 6.1.0.Beta4
>
>
> It should be possible to write:
> declare Foo
> list : List<String>
> end
> While not supported in rules using the mvel dialect, it makes declared types much more readable, and adds some type-safety to java rules.
> Notice that this ticket is NOT related to the possibility of declaring generic classes, such as Foo<T>.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
11 years, 7 months
[JBoss JIRA] (DROOLS-115) Add support for strong negation
by Michael Biarnes Kiefer (JIRA)
[ https://issues.jboss.org/browse/DROOLS-115?page=com.atlassian.jira.plugin... ]
Michael Biarnes Kiefer updated DROOLS-115:
------------------------------------------
Fix Version/s: 6.1.0.Beta4
(was: 6.1.0.Beta3)
> Add support for strong negation
> -------------------------------
>
> Key: DROOLS-115
> URL: https://issues.jboss.org/browse/DROOLS-115
> Project: Drools
> Issue Type: Feature Request
> Security Level: Public(Everyone can see)
> Reporter: Davide Sottara
> Assignee: Davide Sottara
> Priority: Minor
> Fix For: 6.1.0.Beta4
>
>
> Drools "not" operator implements a type of "negation by failure", i.e. not X() behaves as the negation of "exists" or, in other words, translates as "it is NOT asserted that ...".
> However, another form of stronger negation is needed to express conditionals such as "it is asserted that NOT ..."
> It should be possible, then, to assert facts both in a "positive" and "negative" way, to assert THAT and THAT NOT.
> The language should also support a "neg" CE to create "negative" patterns which will match with negative facts. I.e. it should be possible to write rules such as:
> when $p : Person() and Car( owner == $p ) then
> // a positive, matching Car is present in the WM
> when $p : Person() and neg Car( owner == $p ) then
> // a negative, matching Car is present in the WM
> when $p : Person() and not Car( owner == $p ) then
> // neither a positive nor a negative fact exists in the WM
> For a more detailed description and motivation see e.g.:
> https://oxygen.informatik.tu-cottbus.de/publications/wagner/WebRules2Neg.pdf
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
11 years, 7 months
[JBoss JIRA] (DROOLS-112) Allow join constraints in sliding windows
by Michael Biarnes Kiefer (JIRA)
[ https://issues.jboss.org/browse/DROOLS-112?page=com.atlassian.jira.plugin... ]
Michael Biarnes Kiefer updated DROOLS-112:
------------------------------------------
Fix Version/s: 6.1.0.Beta4
(was: 6.1.0.Beta3)
> Allow join constraints in sliding windows
> -----------------------------------------
>
> Key: DROOLS-112
> URL: https://issues.jboss.org/browse/DROOLS-112
> Project: Drools
> Issue Type: Feature Request
> Security Level: Public(Everyone can see)
> Affects Versions: 5.5.0.Final, 6.0.0.Alpha9, 6.0.0.Beta1
> Reporter: Davide Sottara
> Assignee: Mark Proctor
> Priority: Critical
> Fix For: 6.1.0.Beta4
>
>
> When using a sliding window, alpha constraints are evaluated before the window is considered, but beta (join) constraints are evaluated afterwards.
> While it does not usually make a difference when time windows are concerned,
> it DOES make a difference with length windows.
> Imho, a clear warning should be added in the documentation to clarify
> the current behavior.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
11 years, 7 months
[JBoss JIRA] (DROOLS-432) Types declared in a foreign package are processed one at a time
by Michael Biarnes Kiefer (JIRA)
[ https://issues.jboss.org/browse/DROOLS-432?page=com.atlassian.jira.plugin... ]
Michael Biarnes Kiefer updated DROOLS-432:
------------------------------------------
Fix Version/s: 6.1.0.Beta4
(was: 6.1.0.Beta3)
> Types declared in a foreign package are processed one at a time
> ---------------------------------------------------------------
>
> Key: DROOLS-432
> URL: https://issues.jboss.org/browse/DROOLS-432
> Project: Drools
> Issue Type: Bug
> Security Level: Public(Everyone can see)
> Affects Versions: 5.5.0.Final, 5.6.0.Final, 6.0.1.Final
> Reporter: Davide Sottara
> Assignee: Mark Proctor
> Fix For: 6.1.0.Beta4
>
>
> The following snippet has two issues
> {code}
> package a;
> declare b.X field : b.Y end
> declare b.Y end
> {code}
> While processing package a, the packageBuilder will infer the existence of package b and create the appropriate typeDeclarations.
> However, a partial, independent package b is created for X and Y:
> - it is inefficient
> - internal dependencies cannot be resolved : b.X does not (yet) see b.Y
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
11 years, 7 months