[esb-issues] [JBoss JIRA] Commented: (JBESB-1889) bpm_orchestration4 is buggy and documentation is out-fo-date
[
https://jira.jboss.org/jira/browse/JBESB-1889?page=com.atlassian.jira.plu...
]
Burr Sutter commented on JBESB-1889:
------------------------------------
Does the following look better for Priority_Rules.drl:
rule "Logging"
salience 20
when
order: OrderHeader()
customer: Customer()
then
order.setOrderPriority(1);
end
rule "Customer Silver Status"
salience 10
when
customer: Customer(status > 10)
order: OrderHeader(totalAmount > 25)
then
order.setOrderPriority(2);
end
rule "Customer Gold Status"
salience 5
when
customer: Customer(status >= 40)
order: OrderHeader(totalAmount > 50)
then
order.setOrderPriority(3);
end
rule "Customer Diamond Status"
salience 1
when
customer: Customer(status >= 40)
order: OrderHeader(totalAmount > 150)
then
order.setOrderPriority(4);
end
bpm_orchestration4 is buggy and documentation is out-fo-date
------------------------------------------------------------
Key: JBESB-1889
URL: https://jira.jboss.org/jira/browse/JBESB-1889
Project: JBoss ESB
Issue Type: Bug
Security Level: Public(Everyone can see)
Components: Examples
Affects Versions: 4.3
Reporter: Jiri Pechanec
Fix For: 4.x
The documentation for this quickstart is completely out-of-date and metions configuration
that are no longer valid or present in there.
The priority calculation is wrong - the Logging rule sets priority to 1 but its salince
is 10 and fires AFTER priority setting rules. It means that either it should not set the
prority or its salience must be higher than the other rules.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
https://jira.jboss.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira