[JBoss JIRA] Created: (JBPM-1004) add dynamic (late) subprocessresolving based on EL
by Ronald van Kuijk (JIRA)
add dynamic (late) subprocessresolving based on EL
--------------------------------------------------
Key: JBPM-1004
URL: http://jira.jboss.com/jira/browse/JBPM-1004
Project: JBoss jBPM
Issue Type: Feature Request
Environment: N/A
Reporter: Ronald van Kuijk
Assigned To: Tom Baeyens
Priority: Optional
Fix For: jBPM jPDL 3.2.2
Being able to do something like
<process-definition name='superprocess'>
<start-state name='start'>
<transition to='sub process state' />
</start-state>
<process-state name='sub process state'>
<sub-process name='#{mySubProcess}' binding='late'/>
<transition to='wait' />
</process-state>
<state name='wait' />
</process-definition>
Would be great. This way you can have dynamic subprocesses based on e.g. a variable in the process....
--
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, 1 month
[JBoss JIRA] Commented: (JBRULES-313) Add halt/run commands
by Edson Tirelli (JIRA)
[ http://jira.jboss.com/jira/browse/JBRULES-313?page=comments#action_12367185 ]
Edson Tirelli commented on JBRULES-313:
---------------------------------------
Added support to fire limit:
workingMemory.fireAllRules( int fireLimit );
So the rules will fire until agenda is empty or fire limit is reached.
> 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: Edson Tirelli
> Fix For: 4.0.0.MR4
>
>
> 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, 1 month
[JBoss JIRA] Created: (GPD-80) alpha4 eclipse site broken for alpha3 users?
by Edward Staub (JIRA)
alpha4 eclipse site broken for alpha3 users?
--------------------------------------------
Key: GPD-80
URL: http://jira.jboss.com/jira/browse/GPD-80
Project: JBoss jBPM GPD
Issue Type: Bug
Affects Versions: jBPM JPDL Designer 3.1.0.alpha4
Reporter: Edward Staub
Assigned To: Koen Aers
Priority: Critical
Koen,
site.xml was not updated from alpha3.
I'm not sure, but I think I'm seeing this have the effect that, if you have alpha3 installed, trying to install alpha4 results in a "there's nothing new to install here" at the site. While a workaround is easy (delete - NOT DISABLE - alpha3 first), figuring it out is not - hence the "critical" level.
I hope I'm not crying wolf here - apologies in advance if I missed something. I'm not comfortable with Eclipse yet.
If I'm right, you may want to post something on the forum.
-Ed Staub
--
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, 1 month