Re: [rules-users] Drools Flow 5.1 - latest snapshot -- Gateway (Diverge) : Split Node - Priority Does not Work

2010-07-21 Thread Kris Verlaenen
Vijay,

This is a known limitation when using BPMN2.  Check out the documentation, that 
describes which features are implemented already in the BPMN2 implementation:
https://hudson.jboss.org/hudson/job/drools/lastSuccessfulBuild/artifact/trunk/target/docs/drools-flow/html/ch13.html

Priorities are not yet implemented as it seems the BPMN2 spec simply does not 
define something like this.  If we want to support something like this, we will 
probably have to define a custom extension (but we didn't do this yet as we 
wanted to wait until the spec was final before starting to add too much custom 
extensions).

A workaround would be to use mutually exclusive conditions for now ...

Kris

  - Original Message - 
  From: Vijay K Pandey 
  To: rules-users@lists.jboss.org 
  Sent: Wednesday, July 21, 2010 5:45 AM
  Subject: [rules-users] Drools Flow 5.1 - latest snapshot -- Gateway (Diverge) 
: Split Node - Priority Does not Work


  Hi All,

   

  In the Drools Flow 5.1 latest snapshot , for the node (Gateway (Diverge) : 
Split Node), somehow priority does not work. If we set some value, lets say 100 
and open the process file(BPMN2) again and check the priority - somehow it 
doesn't retains the priority value and reports the value always as 0.

   

  I am trying to make use one of the feature of XOR type node where one of the 
constraint is always true with the highest priority. I hope my understanding 
is right.

   

  This is what the Drools Flow Doc says:

   

  XOR means that exactly one of the outgoing connections will be chosen. The 
decision is made by evaluating the constraints that are linked to each of the 
outgoing connections. Constraints are specified using the same syntax as the 
left-hand side of a rule. The constraint with the lowest priority number that 
evaluates to true is selected. Note that you should always make sure that at 
least one of the outgoing connections will evaluate to true at runtime (the 
ruleflow will throw an exception at runtime if it cannot find at least one 
outgoing connection). For example, you could use a connection which is always 
true (default) with a high priority number to specify what should happen if 
none of the other connections can be taken.

   

  Has anyone faced this issue?

   

  Thanks

  Vijay

   



--


  ___
  rules-users mailing list
  rules-users@lists.jboss.org
  https://lists.jboss.org/mailman/listinfo/rules-users

Disclaimer: http://www.kuleuven.be/cwis/email_disclaimer.htm
___
rules-users mailing list
rules-users@lists.jboss.org
https://lists.jboss.org/mailman/listinfo/rules-users


Re: [rules-users] Drools Flow 5.1 - latest snapshot -- Gateway(Diverge) : Split Node - Priority Does not Work

2010-07-21 Thread Kris Verlaenen
Santosh,

I think you need to add it as part of a META-INF directory inside a source dir. 
 There's a screencast that shows you how to get a simple example working, try 
following that and let me know if you still have issues with that:
http://people.redhat.com/kverlaen/DomainSpecificWorkItem.swf

Kris

- Original Message - 
  From: santosh mukherjee 
  To: Rules Users List 
  Sent: Wednesday, July 21, 2010 8:54 AM
  Subject: Re: [rules-users] Drools Flow 5.1 - latest snapshot -- 
Gateway(Diverge) : Split Node - Priority Does not Work


  Hi,


  I have added my MyWorkDefinitions.conf and drools.rulebase.conf file in a 
source folder named resources inside my project. But then also my work items 
are not showing in the flow editor. Can anybody tell me why this is so?


  Thanks
  Santosh Mukherjee.


  2010/7/21 Vijay K Pandey vpan...@mdes.ms.gov

Hi All,



In the Drools Flow 5.1 latest snapshot , for the node (Gateway (Diverge) : 
Split Node), somehow priority does not work. If we set some value, lets say 100 
and open the process file(BPMN2) again and check the priority – somehow it 
doesn’t retains the priority value and reports the value always as 0.



I am trying to make use one of the feature of XOR type node where one of 
the constraint is “always true” with the highest priority. I hope my 
understanding is right.



This is what the Drools Flow Doc says:



XOR means that exactly one of the outgoing connections will be chosen. The 
decision is made by evaluating the constraints that are linked to each of the 
outgoing connections. Constraints are specified using the same syntax as the 
left-hand side of a rule. The constraint with the lowest priority number that 
evaluates to true is selected. Note that you should always make sure that at 
least one of the outgoing connections will evaluate to true at runtime (the 
ruleflow will throw an exception at runtime if it cannot find at least one 
outgoing connection). For example, you could use a connection which is always 
true (default) with a high priority number to specify what should happen if 
none of the other connections can be taken.



Has anyone faced this issue?



Thanks

Vijay




___
rules-users mailing list
rules-users@lists.jboss.org
https://lists.jboss.org/mailman/listinfo/rules-users






--


  ___
  rules-users mailing list
  rules-users@lists.jboss.org
  https://lists.jboss.org/mailman/listinfo/rules-users

Disclaimer: http://www.kuleuven.be/cwis/email_disclaimer.htm
___
rules-users mailing list
rules-users@lists.jboss.org
https://lists.jboss.org/mailman/listinfo/rules-users


Re: [rules-users] Drools Flow 5.1 - latest snapshot -- Gateway (Diverge) : Split Node - Priority Does not Work

2010-07-21 Thread Vijay K Pandey
Thanks Kris.

From: rules-users-boun...@lists.jboss.org 
[mailto:rules-users-boun...@lists.jboss.org] On Behalf Of Kris Verlaenen
Sent: Wednesday, July 21, 2010 4:56 AM
To: rules-users@lists.jboss.org; Vijay K Pandey
Subject: Re: [rules-users] Drools Flow 5.1 - latest snapshot -- Gateway 
(Diverge) : Split Node - Priority Does not Work

Vijay,

This is a known limitation when using BPMN2.  Check out the documentation, that 
describes which features are implemented already in the BPMN2 implementation:
https://hudson.jboss.org/hudson/job/drools/lastSuccessfulBuild/artifact/trunk/target/docs/drools-flow/html/ch13.html

Priorities are not yet implemented as it seems the BPMN2 spec simply does not 
define something like this.  If we want to support something like this, we will 
probably have to define a custom extension (but we didn't do this yet as we 
wanted to wait until the spec was final before starting to add too much custom 
extensions).

A workaround would be to use mutually exclusive conditions for now ...

Kris

- Original Message -
From: Vijay K Pandeymailto:vpan...@mdes.ms.gov
To: rules-users@lists.jboss.orgmailto:rules-users@lists.jboss.org
Sent: Wednesday, July 21, 2010 5:45 AM
Subject: [rules-users] Drools Flow 5.1 - latest snapshot -- Gateway (Diverge) : 
Split Node - Priority Does not Work

Hi All,

In the Drools Flow 5.1 latest snapshot , for the node (Gateway (Diverge) : 
Split Node), somehow priority does not work. If we set some value, lets say 100 
and open the process file(BPMN2) again and check the priority - somehow it 
doesn't retains the priority value and reports the value always as 0.

I am trying to make use one of the feature of XOR type node where one of the 
constraint is always true with the highest priority. I hope my understanding 
is right.

This is what the Drools Flow Doc says:

XOR means that exactly one of the outgoing connections will be chosen. The 
decision is made by evaluating the constraints that are linked to each of the 
outgoing connections. Constraints are specified using the same syntax as the 
left-hand side of a rule. The constraint with the lowest priority number that 
evaluates to true is selected. Note that you should always make sure that at 
least one of the outgoing connections will evaluate to true at runtime (the 
ruleflow will throw an exception at runtime if it cannot find at least one 
outgoing connection). For example, you could use a connection which is always 
true (default) with a high priority number to specify what should happen if 
none of the other connections can be taken.

Has anyone faced this issue?

Thanks
Vijay


___
rules-users mailing list
rules-users@lists.jboss.org
https://lists.jboss.org/mailman/listinfo/rules-users

Disclaimer: http://www.kuleuven.be/cwis/email_disclaimer.htm for more 
information.
___
rules-users mailing list
rules-users@lists.jboss.org
https://lists.jboss.org/mailman/listinfo/rules-users


[rules-users] Drools Flow 5.1 - latest snapshot -- Gateway (Diverge) : Split Node - Priority Does not Work

2010-07-20 Thread Vijay K Pandey
Hi All,

In the Drools Flow 5.1 latest snapshot , for the node (Gateway (Diverge) : 
Split Node), somehow priority does not work. If we set some value, lets say 100 
and open the process file(BPMN2) again and check the priority - somehow it 
doesn't retains the priority value and reports the value always as 0.

I am trying to make use one of the feature of XOR type node where one of the 
constraint is always true with the highest priority. I hope my understanding 
is right.

This is what the Drools Flow Doc says:

XOR means that exactly one of the outgoing connections will be chosen. The 
decision is made by evaluating the constraints that are linked to each of the 
outgoing connections. Constraints are specified using the same syntax as the 
left-hand side of a rule. The constraint with the lowest priority number that 
evaluates to true is selected. Note that you should always make sure that at 
least one of the outgoing connections will evaluate to true at runtime (the 
ruleflow will throw an exception at runtime if it cannot find at least one 
outgoing connection). For example, you could use a connection which is always 
true (default) with a high priority number to specify what should happen if 
none of the other connections can be taken.

Has anyone faced this issue?

Thanks
Vijay

___
rules-users mailing list
rules-users@lists.jboss.org
https://lists.jboss.org/mailman/listinfo/rules-users