[JBoss JIRA] Created: (JBRULES-931) Have defect with JavaBeans as fact.
by Anthony Tran (JIRA)
Have defect with JavaBeans as fact.
-----------------------------------
Key: JBRULES-931
URL: http://jira.jboss.com/jira/browse/JBRULES-931
Project: JBoss Rules
Issue Type: Feature Request
Security Level: Public (Everyone can see)
Components: All
Affects Versions: 3.0.6
Environment: W-XP SP2
Reporter: Anthony Tran
Assigned To: Mark Proctor
Fix For: 3.0.6
I use XMLBeans to generate and compile Java classes at runtime, then parse XML files to be objects of classess which has been compiled. Those objects are added into working memory as facts in my application. JBOSS Rule engine can recognize those facts, but can't bound.
Ex:
rule
when
p:ProductService(type == "monitor")
u:User(product == p)
then
.....
end
The LHS is never fired.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
18 years, 10 months
[JBoss JIRA] Created: (JBRULES-1151) Bulding sources from root folder fails
by Yuri de Wit (JIRA)
Bulding sources from root folder fails
--------------------------------------
Key: JBRULES-1151
URL: http://jira.jboss.com/jira/browse/JBRULES-1151
Project: JBoss Rules
Issue Type: Bug
Security Level: Public (Everyone can see)
Components: All
Affects Versions: 4.0.1
Reporter: Yuri de Wit
Assigned To: Mark Proctor
Tried to build from sources downloaded from the links provided in the mailing list and got the following (mvn package):
[INFO] Scanning for projects...
[INFO] ------------------------------------------------------------------------
[ERROR] FATAL ERROR
[INFO] ------------------------------------------------------------------------
[INFO] Error building POM (may not be this project's POM).
Project ID: unknown
Reason: Could not find the model file 'C:\tools\drools-4.0.1\drools-ant\pom.xml'.
[INFO] ------------------------------------------------------------------------
[INFO] Trace
org.apache.maven.reactor.MavenExecutionException: Could not find the model file 'C:\tools\drools-4.0.1\drools-ant\pom.xm
l'.
at org.apache.maven.DefaultMaven.getProjects(DefaultMaven.java:365)
at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:278)
at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:115)
at org.apache.maven.cli.MavenCli.main(MavenCli.java:256)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
at java.lang.reflect.Method.invoke(Method.java:585)
at org.codehaus.classworlds.Launcher.launchEnhanced(Launcher.java:315)
at org.codehaus.classworlds.Launcher.launch(Launcher.java:255)
at org.codehaus.classworlds.Launcher.mainWithExitCode(Launcher.java:430)
at org.codehaus.classworlds.Launcher.main(Launcher.java:375)
Caused by: org.apache.maven.project.ProjectBuildingException: Could not find the model file 'C:\tools\drools-4.0.1\drool
s-ant\pom.xml'.
at org.apache.maven.project.DefaultMavenProjectBuilder.readModel(DefaultMavenProjectBuilder.java:1274)
at org.apache.maven.project.DefaultMavenProjectBuilder.buildFromSourceFileInternal(DefaultMavenProjectBuilder.ja
va:414)
at org.apache.maven.project.DefaultMavenProjectBuilder.build(DefaultMavenProjectBuilder.java:192)
at org.apache.maven.DefaultMaven.getProject(DefaultMaven.java:515)
at org.apache.maven.DefaultMaven.collectProjects(DefaultMaven.java:447)
at org.apache.maven.DefaultMaven.collectProjects(DefaultMaven.java:491)
at org.apache.maven.DefaultMaven.getProjects(DefaultMaven.java:351)
... 11 more
Caused by: java.io.FileNotFoundException: C:\tools\drools-4.0.1\drools-ant\pom.xml (The system cannot find the path spec
ified)
at java.io.FileInputStream.open(Native Method)
at java.io.FileInputStream.<init>(FileInputStream.java:106)
at java.io.FileReader.<init>(FileReader.java:55)
at org.apache.maven.project.DefaultMavenProjectBuilder.readModel(DefaultMavenProjectBuilder.java:1269)
... 17 more
[INFO] ------------------------------------------------------------------------
[INFO] Total time: < 1 second
[INFO] Finished at: Thu Aug 30 17:28:45 EDT 2007
[INFO] Final Memory: 1M/3M
[INFO] ------------------------------------------------------------------------
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
18 years, 10 months
[JBoss JIRA] Created: (JBRULES-1169) PredicateConstraint and/or MVEL Constraint issue?
by Yuri de Wit (JIRA)
PredicateConstraint and/or MVEL Constraint issue?
-------------------------------------------------
Key: JBRULES-1169
URL: http://jira.jboss.com/jira/browse/JBRULES-1169
Project: JBoss Rules
Issue Type: Bug
Security Level: Public (Everyone can see)
Affects Versions: 4.0.1
Reporter: Yuri de Wit
Assigned To: Mark Proctor
Priority: Critical
Consider the following rules:
rule (1)
when
a: Criteria(
$criteriaA : criteriaA,
$criteriaB : criteriaB
)
b: Criteria(
matchCriteriaA == true && criteriaA == $criteriaA
|| matchCriteriaB == true && criteriaB == $criteriaB
)
then
...
end
rule (2)
when
a: Criteria(
$criteriaA : criteriaA,
$criteriaB : criteriaB
)
b: Criteria(
eval(
matchCriteriaA == true && criteriaA == $criteriaA
|| matchCriteriaB == true && criteriaB == $criteriaB
)
)
then
...
end
I am seeing different behavior for the same test cases. I am basically inserting
"a" and "b" with matching criteriaA and criteriaB and I am testing different
combinations of matchCriteriaA and matchCriteriaB (i.e. F/F, F/T, T/F, T/T).
Results for rule (1):
F/F -> rule activated (incorrect)
T/F -> rule activated (correct)
F/T -> rule activated (correct)
Results for rule (2):
F/F -> rule activated (incorrect)
T/F -> rule activated (correct)
F/T -> rule activated (correct)
I also tried an eval column (now a snippet based on the actual rule I ran):
eval(
($t_matchDvpAccount == true && $t_accountCode == $c_accountCode)
|| ($t_matchPartialAccount == true && $t_accountCode5 == $c_accountCode5)
|| ($t_matchClientAccount == true && $t_clientAccountCode == $c_accountCode)
|| ($t_matchNoAccount == true)
)
And with the following data (took while debugging the evaluation):
$t_matchClientAccount Boolean (id=176) value false
$t_accountCode "123450ACCT"
$t_matchDvpAccount Boolean (id=176) value false
$t_matchPartialAccount Boolean (id=191) value true
$t_clientAccountCode "12345CACCT"
$c_accountCode5 "12345"
$t_accountCode5 "12345"
$t_matchNoAccount Boolean (id=176) value false
The evaluation returns false.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
18 years, 10 months
[JBoss JIRA] Created: (JBRULES-1156) WorkingMemoryFileLogger is raising NPE for rules containing unbalanced OR CEs
by Edson Tirelli (JIRA)
WorkingMemoryFileLogger is raising NPE for rules containing unbalanced OR CEs
-----------------------------------------------------------------------------
Key: JBRULES-1156
URL: http://jira.jboss.com/jira/browse/JBRULES-1156
Project: JBoss Rules
Issue Type: Bug
Security Level: Public (Everyone can see)
Components: Reteoo
Affects Versions: 4.0.1
Reporter: Edson Tirelli
Assigned To: Edson Tirelli
Fix For: 4.0.2
Apply WorkingMemoryFileLogger for rules like the following and it will raise the NPE:
rule "Your First Rule"
#include attributes such as "salience" here...
when
(or
not Venue()
(and v:Venue()
l:ListeSousVenue()
p:Param()))
then
#actions
System.out.println("OK - 1");
end
rule "Your Second Rule"
#include attributes such as "salience" here...
when
(or
not Venue()
(and p:Param()
l:ListeSousVenue()
v:Venue()))
then
#actions
System.out.println("OK - 2");
end
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
18 years, 10 months