[esb-issues] [JBoss JIRA] Commented: (JBESB-1889) bpm_orchestration4 is buggy and documentation is out-fo-date

[Jiri Pechanec (JIRA)]

    [ https://jira.jboss.org/jira/browse/JBESB-1889?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12422895#action_12422895 ] 

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