[esb-issues] [JBoss JIRA] Commented: (JBESB-1801) bpm_orchestration3 quickstart documentation has to be revisited
Burr Sutter (JIRA)
jira-events at lists.jboss.org
Tue Jun 10 08:43:16 EDT 2008
[ http://jira.jboss.com/jira/browse/JBESB-1801?page=comments#action_12416262 ]
Burr Sutter commented on JBESB-1801:
------------------------------------
Actually, bpm_orchestration3 shouldn't be using tokenID at all any more. The new version of bpm_orchestration3 uses a file listener and some groovy code to trigger the callback service. Signal & tokenID have been deprecated in ESB 4.3 and SOA-P 4.2 GA+.
> bpm_orchestration3 quickstart documentation has to be revisited
> ---------------------------------------------------------------
>
> Key: JBESB-1801
> URL: http://jira.jboss.com/jira/browse/JBESB-1801
> Project: JBoss ESB
> Issue Type: Bug
> Security Level: Public(Everyone can see)
> Components: Examples
> Affects Versions: 4.2.1 CP3
> Environment: Embedded, production
> Reporter: Jiri Pechanec
> Assigned To: Kevin Conner
> Priority: Minor
> Fix For: 4.2.1 CP4
>
>
> 1) At the beginning the quickstart prints
> 2008-06-10 09:28:39,460 INFO [org.jboss.soa.esb.samples.quickstarts.bpm_orchestration3.esb_actions.SetupKey] --------------------------------
> 2008-06-10 09:28:39,460 INFO [org.jboss.soa.esb.samples.quickstarts.bpm_orchestration3.esb_actions.SetupKey] businessKey: Demo1
> 2008-06-10 09:28:39,461 INFO [org.jboss.soa.esb.samples.quickstarts.bpm_orchestration3.esb_actions.SetupKey] Body: Hello start
> 2008-06-10 09:28:39,461 INFO [org.jboss.soa.esb.samples.quickstarts.bpm_orchestration3.esb_actions.SetupKey] --------------------------------
> which is not mentioned
> 2) The step that talks about signalling process mixes apples with oranges - it speaks about process id but token id should be used - so has to go to list of tokens for process. The token id and process id can have different values
> 3) The text
> [SetupSignal] --------------------------------
> [SetupSignal] jbpmTokenId: 1
> [SetupSignal] Body: Hello Signal
> [SetupSignal] --------------------------------
> is not printed second time
> 4) This note should not be included or rephrased to omit link millisToWaitForResponse
> Note: There is NO <millisToWaitForResponse>5000</millisToWaitForResponse>^M
> therefore is no waiting for a response from the ESB. The request is^M
> made asynchronously to the ESB Service and the process instance enters a wait-state.^M
> It goes to sleep and waits some external "signal". A waiting/sleeping^M
> process instance is held in the database.^M
--
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
More information about the esb-issues
mailing list