[JBoss JIRA] (DROOLS-1448) [XLS Decision Table] Integer values for Double attributes causes validation error
by Jozef Marko (JIRA)
[ https://issues.jboss.org/browse/DROOLS-1448?page=com.atlassian.jira.plugi... ]
Jozef Marko updated DROOLS-1448:
--------------------------------
Component/s: XLS Decision Table Editor
> [XLS Decision Table] Integer values for Double attributes causes validation error
> ---------------------------------------------------------------------------------
>
> Key: DROOLS-1448
> URL: https://issues.jboss.org/browse/DROOLS-1448
> Project: Drools
> Issue Type: Bug
> Components: XLS Decision Table Editor
> Affects Versions: 7.0.0.Beta6
> Reporter: Jozef Marko
> Assignee: Mario Fusco
> Priority: Minor
> Labels: dtable_testday_preparation, qe-test-day, reported-by-qe
> Attachments: Driver.java, ExamplePolicyPricing.xls, Policy.java, Screenshot from 2017-02-02 10-22-21.png
>
>
> If the XLS decision contains Integer values for column ( attribute ) that is Double data type, then the XLS decision table is not validated successfully. After conversion to guided decision table is the table validated successfully.
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
8 years
[JBoss JIRA] (DROOLS-1202) I am not able to assign keys to Enum value through external data objects
by Michael Anstis (JIRA)
[ https://issues.jboss.org/browse/DROOLS-1202?page=com.atlassian.jira.plugi... ]
Michael Anstis commented on DROOLS-1202:
----------------------------------------
[~jomarko] It is not possible to mix and match Java enumerations and MVEL-based enumerations.
IMO it should be closed as "Will not fix" with the recommendation to use MVEL-based enumerations if key/value mapping is required.
> I am not able to assign keys to Enum value through external data objects
> ------------------------------------------------------------------------
>
> Key: DROOLS-1202
> URL: https://issues.jboss.org/browse/DROOLS-1202
> Project: Drools
> Issue Type: Bug
> Reporter: Fatema Rangwala
> Assignee: Mark Proctor
> Labels: drools-tools
> Attachments: TestEnumPrac.java
>
>
> I was able to import Enum through data objects in workbench. But when I tried to add keys to enum value it is not supported.
> For e.g. in workbench it is supported to assign keys to enum value like [F='Female', M='Male'].
> But not able to assign keys to enum using external data object.
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
8 years
[JBoss JIRA] (DROOLS-365) Rule attribute for adding inverse of consequence as rule condition
by Jozef Marko (JIRA)
[ https://issues.jboss.org/browse/DROOLS-365?page=com.atlassian.jira.plugin... ]
Jozef Marko resolved DROOLS-365.
--------------------------------
Resolution: Done
> Rule attribute for adding inverse of consequence as rule condition
> ------------------------------------------------------------------
>
> Key: DROOLS-365
> URL: https://issues.jboss.org/browse/DROOLS-365
> Project: Drools
> Issue Type: Feature Request
> Affects Versions: 5.5.0.Final
> Reporter: Adar Dembo
> Assignee: Mark Proctor
>
> I have quite a few rules that look like this:
> {noformat}
> rule "if foo then bar"
> when
> Foo($a : a, $b : b)
> not Bar(a == $a, b == $b)
> then
> insert(new Bar($a, $b));
> end
> {noformat}
> This is a fairly common pattern for me: a rule should not activate if the facts generated by its consequence were already asserted. It's a pattern I use extensively to generate linear (i.e. non-repeating) workflows.
> Ideally I'd be able to express it as follows:
> {noformat}
> rule "if foo then bar"
> condition-on-inverse-of-consequence
> when
> Foo($a : a, $b : b)
> then
> insert(new Bar($a, $b));
> end
> {noformat}
> And {{condition-on-inverse-of-consequence}} would cause Drools to generate the right kind of condition, which would be the inverse of the fact changes made by the consequence.
> I think {{lock-on-active}} is similar but harsher: it prevents the rule from firing a second time altogether, regardless of input. At least, that's based on my reading of the docs. In my example, that would be equivalent to {{not Bar()}} condition in the rule, which is stricter than {{not Bar(a == $a, b == $b)}}.
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
8 years
[JBoss JIRA] (DROOLS-658) External POJOs not shown in Workbench after reopen the project
by Michael Anstis (JIRA)
[ https://issues.jboss.org/browse/DROOLS-658?page=com.atlassian.jira.plugin... ]
Michael Anstis updated DROOLS-658:
----------------------------------
Labels: (was: drools-tools)
> External POJOs not shown in Workbench after reopen the project
> --------------------------------------------------------------
>
> Key: DROOLS-658
> URL: https://issues.jboss.org/browse/DROOLS-658
> Project: Drools
> Issue Type: Bug
> Affects Versions: 6.1.0.Final, 6.2.0.CR2, 6.3.0.CR1
> Environment: linux 64 bits, EAP 6.4, java version "1.6.0_45"
> Reporter: Jose Cavieres
> Assignee: Walter Medvedeo
> Attachments: Dependency.jpeg, Reusable-1.0.jar, Reusable-1.0.pom, dependecy-top.jpeg, error-top.jpeg, new-class-types.jpeg, reuse.tgz
>
>
> In order to reuse some POJOs, I followed the procedure defined in
> http://mswiderski.blogspot.com/2014/02/reuse-your-business-assets-with-jb...
> and added a POJO to the "reusable project" (named Papito)
> Everything works fine the first time one uses those clases in the "top project" (named Hijita) . POJOs of the "reusable project" are prefixed with the string "- ext -" in the Java editor of the "top project" just as explained in "15.7.6.6.3. Using the external objects" of the document:
> http://docs.jboss.org/drools/release/6.1.0.Final/drools-docs/html/wb.Work...
> The problem is that only happens the first time. If one logout and the login again, the "-ext" classes are no longer shown as valid Types por the POJOs in the "top project"
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
8 years
[JBoss JIRA] (DROOLS-658) External POJOs not shown in Workbench after reopen the project
by Michael Anstis (JIRA)
[ https://issues.jboss.org/browse/DROOLS-658?page=com.atlassian.jira.plugin... ]
Michael Anstis reassigned DROOLS-658:
-------------------------------------
Assignee: Walter Medvedeo (was: Michael Anstis)
> External POJOs not shown in Workbench after reopen the project
> --------------------------------------------------------------
>
> Key: DROOLS-658
> URL: https://issues.jboss.org/browse/DROOLS-658
> Project: Drools
> Issue Type: Bug
> Affects Versions: 6.1.0.Final, 6.2.0.CR2, 6.3.0.CR1
> Environment: linux 64 bits, EAP 6.4, java version "1.6.0_45"
> Reporter: Jose Cavieres
> Assignee: Walter Medvedeo
> Attachments: Dependency.jpeg, Reusable-1.0.jar, Reusable-1.0.pom, dependecy-top.jpeg, error-top.jpeg, new-class-types.jpeg, reuse.tgz
>
>
> In order to reuse some POJOs, I followed the procedure defined in
> http://mswiderski.blogspot.com/2014/02/reuse-your-business-assets-with-jb...
> and added a POJO to the "reusable project" (named Papito)
> Everything works fine the first time one uses those clases in the "top project" (named Hijita) . POJOs of the "reusable project" are prefixed with the string "- ext -" in the Java editor of the "top project" just as explained in "15.7.6.6.3. Using the external objects" of the document:
> http://docs.jboss.org/drools/release/6.1.0.Final/drools-docs/html/wb.Work...
> The problem is that only happens the first time. If one logout and the login again, the "-ext" classes are no longer shown as valid Types por the POJOs in the "top project"
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
8 years