[JBoss JIRA] Created: (JBRULES-520) How to refer one rule in another
by Sridhar Ramaswamy (JIRA)
How to refer one rule in another
--------------------------------
Key: JBRULES-520
URL: http://jira.jboss.com/jira/browse/JBRULES-520
Project: JBoss Rules
Issue Type: Feature Request
Security Level: Public (Everyone can see)
Affects Versions: 3.0.4
Environment: WSAD
Reporter: Sridhar Ramaswamy
Assigned To: Mark Proctor
I have the following three rules created in a drl:
rule "Sales"
when
abc: abcData( $abcName : abcName,
$value: value > 20)
then
abc.setFlagColor("RED");
end
rule "Count"
when
bcd: bcdData( $bcdName : bcdName,
$count: count < 120)
then
abc.setFlagColor("RED");
end
How to create a new rule which will use these rules, for instance
rule "sales & count"
when
either rule "sales" is true or "count" is true
and
aaa: aaaData($aaaName: aaaName, $amount: amount < 1000)
then
aaa.setFlag("Critical");
end
I am not able to call a rule into another rule to check that is also true.
Thanks/Sri.
--
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
19 years, 2 months
[JBoss JIRA] Updated: (JBRULES-313) Add halt/run commands
by Mark Proctor (JIRA)
[ http://jira.jboss.com/jira/browse/JBRULES-313?page=all ]
Mark Proctor updated JBRULES-313:
---------------------------------
Summary: Add halt/run commands (was: Add ability to pause rule firing.)
Fix Version/s: 4.0.0.MR3
Affects Version/s: (was: 3.0.1)
> Add halt/run commands
> ---------------------
>
> Key: JBRULES-313
> URL: http://jira.jboss.com/jira/browse/JBRULES-313
> Project: JBoss Rules
> Issue Type: Feature Request
> Security Level: Public(Everyone can see)
> Environment: any
> Reporter: Jacek Jarmulak
> Assigned To: Mark Proctor
> Fix For: 4.0.0.MR3
>
>
> I have made a small modification to WorkingMemory and AbstractWorkingMemory that allows me to pause and the restart rule firing.
> The change consists of adding a boolean isPaused flag (plus gettter and setter methods) which is then inspected in the while loop of the fireAllRules method as follows
> public synchronized void fireAllRules(final AgendaFilter agendaFilter) throws FactException {
> if ( !this.firing ) {
> try {
> this.firing = true;
> while ( !this.isPaused() && this.agenda.fireNextItem( agendaFilter ) ) {
> ;
> }
> } finally {
> this.firing = false;
> }
> }
> }
> What is this good for?
> It lets me stop rule firing from within some rule, e.g. when I want to execute an external call.
> The rule sets up the call and then calls setPaused(true) on WorkingMemory.
> Once fireAllRules exits, an external process executes the call, possibly asserting some facts into WorkingMemory
> and then calls setPaused(false) and calls fireAllRules again.
> Why not execute the call directly from the rule?
> Because in my application the execution might take long time, and I want to have an option to move the WorkingMemory out of RAM,
> possibly moving it to another app server to continue firing after the externall call processing has completed.
--
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
19 years, 2 months
[JBoss JIRA] Commented: (JBRULES-313) Add ability to pause rule firing.
by Mark Proctor (JIRA)
[ http://jira.jboss.com/jira/browse/JBRULES-313?page=comments#action_12363657 ]
Mark Proctor commented on JBRULES-313:
--------------------------------------
typically this is called "halt" and "run", I should be adding those shortly.
> Add ability to pause rule firing.
> ---------------------------------
>
> Key: JBRULES-313
> URL: http://jira.jboss.com/jira/browse/JBRULES-313
> Project: JBoss Rules
> Issue Type: Feature Request
> Security Level: Public(Everyone can see)
> Environment: any
> Reporter: Jacek Jarmulak
> Assigned To: Mark Proctor
> Fix For: 4.0.0.MR3
>
>
> I have made a small modification to WorkingMemory and AbstractWorkingMemory that allows me to pause and the restart rule firing.
> The change consists of adding a boolean isPaused flag (plus gettter and setter methods) which is then inspected in the while loop of the fireAllRules method as follows
> public synchronized void fireAllRules(final AgendaFilter agendaFilter) throws FactException {
> if ( !this.firing ) {
> try {
> this.firing = true;
> while ( !this.isPaused() && this.agenda.fireNextItem( agendaFilter ) ) {
> ;
> }
> } finally {
> this.firing = false;
> }
> }
> }
> What is this good for?
> It lets me stop rule firing from within some rule, e.g. when I want to execute an external call.
> The rule sets up the call and then calls setPaused(true) on WorkingMemory.
> Once fireAllRules exits, an external process executes the call, possibly asserting some facts into WorkingMemory
> and then calls setPaused(false) and calls fireAllRules again.
> Why not execute the call directly from the rule?
> Because in my application the execution might take long time, and I want to have an option to move the WorkingMemory out of RAM,
> possibly moving it to another app server to continue firing after the externall call processing has completed.
--
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
19 years, 2 months
[JBoss JIRA] Closed: (JBRULES-305) Provide a "not matches" field constraint
by Mark Proctor (JIRA)
[ http://jira.jboss.com/jira/browse/JBRULES-305?page=all ]
Mark Proctor closed JBRULES-305.
--------------------------------
Resolution: Duplicate Issue
This is already fixed here JBRULES-231 for part of 4.0, we will not backport this to 3.0.x
> Provide a "not matches" field constraint
> ----------------------------------------
>
> Key: JBRULES-305
> URL: http://jira.jboss.com/jira/browse/JBRULES-305
> Project: JBoss Rules
> Issue Type: Feature Request
> Security Level: Public(Everyone can see)
> Components: Reteoo
> Affects Versions: 3.0.1
> Environment: N/A
> Reporter: Andy Gerweck
> Assigned To: Mark Proctor
>
> JBoss Rules really should have a "not matches" regular expression operator to complement "matches". There's currently no language construct to directly support something like this:
> rule
> when
> Email(from matches "me@.*", to !matches "you@.*)
> then
> doSomething();
> end
> It's possible to do this using a predicate expression, but JBoss just carried an article (rightly) condemning Java in rules! We already have negations of all the other operators (!=/==, </>=, contains/excludes).
--
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
19 years, 2 months
[JBoss JIRA] Created: (JBPORTAL-1405) First Pass CMS Portlet UI Improvements
by Julien Viet (JIRA)
First Pass CMS Portlet UI Improvements
--------------------------------------
Key: JBPORTAL-1405
URL: http://jira.jboss.com/jira/browse/JBPORTAL-1405
Project: JBoss Portal
Issue Type: Task
Security Level: Public (Everyone can see)
Affects Versions: 2.6.CR2
Reporter: Julien Viet
Assigned To: Sohil Shah
Fix For: 2.6 Final
The select Action drop down has a small triangle to the left of it, along with all of the items in the drop down. These should be removed.
The search function for CMS is unclear. There doesn't appear to be any documentation for it, and it doesn't act like a user would expect. I'm guessing the reason is that the box is passing the query text to the lucene full text search, and it seems to expect Lucene's query syntax. The search sytax should be simplified to search for content item names, or text in content, but these options should be explicitly noted, or options that the user can choose between.
Content items should be allowed to be renamed.
CMS Search
There should be an action that allows the user to go back to the main CMS screen whether content items are found or not.
--
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
19 years, 2 months
[JBoss JIRA] Created: (JBPORTAL-1465) move and copy commands jump the permissions
by Luca Stancapiano (JIRA)
move and copy commands jump the permissions
-------------------------------------------
Key: JBPORTAL-1465
URL: http://jira.jboss.com/jira/browse/JBPORTAL-1465
Project: JBoss Portal
Issue Type: Bug
Security Level: Public (Everyone can see)
Components: Portal CMS
Affects Versions: 2.6.Beta1
Environment: eclipse , jboss as 4.0.5-cp4 and jboss portal taken from http://anonsvn.jboss.org/repos/portal/trunk
Reporter: Luca Stancapiano
Assigned To: Sohil Shah
Fix For: 2.6 Final
When I log with an administrator different by "admin", I go into cms pannel of portal and I try to copy or move a file from a allowed space to a denied space, I have the error message that advise me that I haven't privileges to take that operation. But if I logout and then I enter again, I go into cms pannel and I see that my operation is succesfully done because the file is moved or copied anyway. Of course then I cannot to remove it because I've not permission in that zone. You can to test that operation moving default/support.html into / that ,in default, is allowed only to "admin" user. I've seen into the code that the permission access for copy and move operations is only for "from" path and there is no control for the "to" path Seeing method "hasManageAccess" into org.jboss.portal.cms.impl.jcr.command.ACLEnforcer class there is:
else if(command instanceof MoveCommand)
{
path = ((MoveCommand)command).msFromPath;
}
and the same thing for copy command.
I modified this part in this mode:
else if(command instanceof MoveCommand)
{
path = ((MoveCommand)command).msFromPath;
hasManageAccess = this.computeAccess(user,path,"manage");
if (hasManageAccess)
{
path = ((MoveCommand)command).msToPath;
hasManageAccess = this.computeAccess(user,path,"manage");
}
}
adding permission control for "to" path. It seems ok. May you try?
--
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
19 years, 2 months