9:41 a.m.
bpm_orchestration4 is not working as expected
---------------------------------------------
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.4
The documentation for this quickstart is completely out-of-date and metions configuration
that are no longer valid or present in there.
Moreover the discount calculation is based on order priority but this one is neither
provided in sample files and parsed/populated in Smooks transformation nor mentioned in
documentation to be set in the first generated task. Thus the discount is not calculated
at all.
--
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
9:46 a.m.
New subject: [JBoss JIRA] Updated: (JBESB-1889) bpm_orchestration4 is out-of-date
[
https://jira.jboss.org/jira/browse/JBESB-1889?page=com.atlassian.jira.plu...
]
Jiri Pechanec updated JBESB-1889:
---------------------------------
Summary: bpm_orchestration4 is out-of-date (was: bpm_orchestration4 is not
working as expected)
Description:
The documentation for this quickstart is completely out-of-date and metions configuration
that are no longer valid or present in there.
Moreover the discount calculation is based on order priority but this one is neither
provided in sample files and parsed/populated in
was:
The documentation for this quickstart is completely out-of-date and metions configuration
that are no longer valid or present in there.
Moreover the discount calculation is based on order priority but this one is neither
provided in sample files and parsed/populated in Smooks transformation nor mentioned in
documentation to be set in the first generated task. Thus the discount is not calculated
at all.
bpm_orchestration4 is out-of-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.4
The documentation for this quickstart is completely out-of-date and metions configuration
that are no longer valid or present in there.
Moreover the discount calculation is based on order priority but this one is neither
provided in sample files and parsed/populated in
--
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
10:18 a.m.
New subject: [JBoss JIRA] Updated: (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...
]
Jiri Pechanec updated JBESB-1889:
---------------------------------
Summary: bpm_orchestration4 is buggy and documentation is out-fo-date (was:
bpm_orchestration4 is out-of-date)
Description:
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.
was:
The documentation for this quickstart is completely out-of-date and metions configuration
that are no longer valid or present in there.
Moreover the discount calculation is based on order priority but this one is neither
provided in sample files and parsed/populated in
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.4
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
10:35 a.m.
New subject: [JBoss JIRA] Updated: (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...
]
Kevin Conner updated JBESB-1889:
--------------------------------
Fix Version/s: 4.x
(was: 4.4)
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
1:23 p.m.
New subject: [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
1:28 p.m.
New subject: [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:
------------------------------------
The docs mention signal & millisToWaitForResponse which was the older way of handling
jBPM to ESB interaction. Are these the specific concerns for this doc?
Any other items?
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
4:09 p.m.
New subject: [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...
]
Jiri Pechanec commented on JBESB-1889:
--------------------------------------
Customer ... Status rules can have the same salience value - it is also logical to have
it
Page 9 - object paths - now esbToBpmVars and mapping
Page 10 - key field is visible
Page 12 - signal
Page 21 - now bpmToEsbPath and esbToBpmPath
- millisToWaitForResponse
It is everything I was able to find
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
4:18 p.m.
New subject: [JBoss JIRA] Assigned: (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 reassigned JBESB-1889:
----------------------------------
Assignee: Burr Sutter
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
Assignee: Burr Sutter
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
9:17 p.m.
New subject: [JBoss JIRA] Work started: (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...
]
Work on JBESB-1889 started by Burr Sutter.
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
Assignee: Burr Sutter
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
9:37 p.m.
New subject: [JBoss JIRA] Resolved: (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 resolved JBESB-1889.
--------------------------------
Resolution: Done
Commits: 21298,21299,21300
Fixed up the Readme.odt, Readme.pdf, Discount_Rules.drl, Priority_Rules.drl, jboss-esb.xml
and processDefinition.xml
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
Assignee: Burr Sutter
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
10:24 a.m.
New subject: [JBoss JIRA] Closed: (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...
]
Kevin Conner closed JBESB-1889.
-------------------------------
Fix Version/s: 4.4
(was: 4.x)
Resolution: Done
Closing against 4.4
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
Assignee: Burr Sutter
Fix For: 4.4
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
10:24 a.m.
New subject: [JBoss JIRA] Reopened: (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...
]
Kevin Conner reopened JBESB-1889:
---------------------------------
Reopening as this task had already been moved out of the 4.4 release
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
Assignee: Burr Sutter
Fix For: 4.4
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
5813
days inactive
5815
days old
11 comments
3 participants
participants (3)
-
Burr Sutter (JIRA) -
Jiri Pechanec (JIRA)
-
Kevin Conner (JIRA)