July 2007 - esb-issues - Jboss List Archives

[JBoss JIRA] Created: (JBESB-734) bpm-based quickstarts don't allow for a signal from jBPM 3.2.1 Admin Console

by Burr Sutter (JIRA)

bpm-based quickstarts don't allow for a signal from jBPM 3.2.1 Admin Console ---------------------------------------------------------------------------- Key: JBESB-734 URL: http://jira.jboss.com/jira/browse/JBESB-734 Project: JBoss ESB Issue Type: Bug Security Level: Public (Everyone can see) Reporter: Burr Sutter Assigned To: Mark Little bpm-based quickstarts don't allow for a signal from jBPM 3.2.1 Admin Console, it currently throws an exception when the user clicks the "signal" link. -- 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

17 years, 7 months

3
7
0 / 0

[JBoss JIRA] Created: (JBESB-688) quickstart jbpm_simple1 remove or rename

by Burr Sutter (JIRA)

quickstart jbpm_simple1 remove or rename ---------------------------------------- Key: JBESB-688 URL: http://jira.jboss.com/jira/browse/JBESB-688 Project: JBoss ESB Issue Type: Bug Security Level: Public (Everyone can see) Reporter: Burr Sutter Assigned To: Mark Little quickstart jbpm_simple1has been showed either follow the bpm_orchestration naming convention OR simply be removed. The majority of its functionality is more cleanly depicted in bpm_orchestration1. the jbpm_simple1 process definition is also difficult (if not impossible) to edit via the jBPM Graphical Process Designer. users should be referred to bpm_orchestration1 as the best starting point. -- 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

17 years, 7 months

3
6
0 / 0

[JBoss JIRA] Created: (JBESB-750) Process definition for bpm_orchestration2 contains refernce to class from bpm_orchestration1

by Jiri Pechanec (JIRA)

Process definition for bpm_orchestration2 contains refernce to class from bpm_orchestration1 --------------------------------------------------------------------------------------------- Key: JBESB-750 URL: http://jira.jboss.com/jira/browse/JBESB-750 Project: JBoss ESB Issue Type: Bug Security Level: Public (Everyone can see) Components: Examples Affects Versions: 4.2 Milestone Release 3 Reporter: Jiri Pechanec Assigned To: Mark Little Priority: Optional The start node in bpm_orchestration2 process definition uses class MyBPMActionHandler from package bpm_orchestration1 and it is not guaranteed that this one will be on classpath. -- 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

17 years, 7 months

3
2
0 / 0

[JBoss JIRA] Created: (JBESB-695) ESBActionHandler needs to refactored to allow for async calls

by Burr Sutter (JIRA)

ESBActionHandler needs to refactored to allow for async calls ------------------------------------------------------------- Key: JBESB-695 URL: http://jira.jboss.com/jira/browse/JBESB-695 Project: JBoss ESB Issue Type: Task Security Level: Public (Everyone can see) Components: BPM Affects Versions: 4.2 Milestone Release 2 Reporter: Burr Sutter Assigned To: Mark Little Fix For: 4.2 >From Jeff Delong, this feedback is based on the quickstarts as well as a flaw in the ESBActionHandler If the ActionHandler does the work of the node (i.e., it invokes the service that does the work of the node), then it should be configured on an action of that node, not on an event. Events are for performing actions that are ancillary to the node, not it's main purpose. Now this raises and issue with the current design of the ESBActionHander. If the service at the node executes asynchronously, then the ESBActionHandler should not signal; instead the service should signal back through the ESB SignalAction. However, if the service should execute synchronously, then the ESBAcionHandler should propogate the token (i.e., do token.signal()). I.e., modify the following code in ESBActionHandler if (null==millisToWaitForResponse || millisToWaitForResponse < 1) { // ASYNC Invoker.invoke(request,esbCategoryName, esbServiceName); return; } Message response = null; if ("MOCK_CATEGORY".equals(esbCategoryName) && "MOCK_SERVICE".equals(esbServiceName)) response = request; else Invoker.invokeAndAwaitResponse (request,esbCategoryName, esbServiceName, millisToWaitForResponse); if (null!=response) varsFromResponse(response); token.signal(); // this is required since the response is sync } Putting the ESBActionHandler on the node-enter, the token will always go on to the next node; since there is no action configured on the node, it moves on by default. Thus the current code will work for sync when configured on a node-enter event, but not work for async on a node-enter event. The current code will NOT work for sync when moved to a node action, but will work for async. In order to make both async and sync work, but the ESBActionHandler on a node action, and add token.signal() to the synch logic. -- 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

17 years, 7 months

3
4
0 / 0

[JBoss JIRA] Created: (JBESB-581) Stateless EPR failover

by Mark Little (JIRA)

Stateless EPR failover ---------------------- Key: JBESB-581 URL: http://jira.jboss.com/jira/browse/JBESB-581 Project: JBoss ESB Issue Type: Task Security Level: Public (Everyone can see) Components: Registry and Repository Affects Versions: 4.2 Milestone Release 2 Reporter: Mark Little Assigned To: Kurt Stam Priority: Critical Fix For: 4.2 As discussed, make sure that we can offer automatic support for ignorning stale EPRs in the registry and, for stateless services, failover/rebinding. -- 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

17 years, 7 months

2
4
0 / 0

[JBoss JIRA] Created: (JBESB-678) Remove retry hard-coded magic number

by Mark Little (JIRA)

Remove retry hard-coded magic number ------------------------------------ Key: JBESB-678 URL: http://jira.jboss.com/jira/browse/JBESB-678 Project: JBoss ESB Issue Type: Task Security Level: Public (Everyone can see) Components: Transports Affects Versions: 4.2 Milestone Release 3 Reporter: Mark Little Assigned To: Mark Little Fix For: 4.2 ServiceInvoker appears to retry deliver twice: private Message deliver(Message message, boolean synchronous) throws MessageDeliverException { int numberOfAttemps=0; while (numberOfAttemps++ < 2) { 2 is an arbitrary number. Rather than hard-code it, it should be configurable, at least via a run-time property. -- 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

17 years, 7 months

2
7
0 / 0

[JBoss JIRA] Created: (JBESB-623) Bring Hudson CI builds inline with current CI builds

by Kevin Conner (JIRA)

Bring Hudson CI builds inline with current CI builds ---------------------------------------------------- Key: JBESB-623 URL: http://jira.jboss.com/jira/browse/JBESB-623 Project: JBoss ESB Issue Type: Task Security Level: Public (Everyone can see) Components: Testing Reporter: Kevin Conner Assigned To: Prabhat Jha The CI build has beem migrated to Hudson but there are a number of outstanding issued to be addressed before it will replace the current CI builds in Newcastle. Current issues are as follows - Hudson should start a build as soon as possible after modifications have been made to the repository. At present the Newcastle CI build checks every 15 mins for modifications, initiating a build when the repository has been updated - Emails should be sent on every build, whether successful or not and contain the following information List of modifications identified Contents of Emma coverage reports - Hudson builds must be reliable. One issue identified so far is a transient clash on port 8888. -- 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

17 years, 7 months

3
11
0 / 0

[JBoss JIRA] Created: (JBESB-747) Changed body contents is not propagated

by Jiri Pechanec (JIRA)

Changed body contents is not propagated --------------------------------------- Key: JBESB-747 URL: http://jira.jboss.com/jira/browse/JBESB-747 Project: JBoss ESB Issue Type: Bug Security Level: Public (Everyone can see) Components: BPM, Rosetta Affects Versions: 4.2 Milestone Release 3 Reporter: Jiri Pechanec Assigned To: Mark Little Priority: Critical When the message body is manipulated inside the service called from BPM then the changed message is not propagated back to BPM engine. See bpm_orchestration1 for example of this behaviour. -- 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

17 years, 7 months

2
5
0 / 0

[JBoss JIRA] Created: (JBESB-640) Fault as a separate message

by Mark Little (JIRA)

Fault as a separate message --------------------------- Key: JBESB-640 URL: http://jira.jboss.com/jira/browse/JBESB-640 Project: JBoss ESB Issue Type: Task Security Level: Public (Everyone can see) Components: Rosetta Affects Versions: 4.2 Milestone Release 2 Reporter: Mark Little Assigned To: Mark Little Fix For: 5.0 Milestone Release 1 Fault should be a separate type of Message and not wrapped within the current Message abstraction. -- 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

17 years, 7 months

1
2
0 / 0

[JBoss JIRA] Created: (JBESB-566) Typed objects from messages

by Mark Little (JIRA)

Typed objects from messages --------------------------- Key: JBESB-566 URL: http://jira.jboss.com/jira/browse/JBESB-566 Project: JBoss ESB Issue Type: Task Security Level: Public (Everyone can see) Components: Rosetta Reporter: Mark Little Assigned To: Mark Little Fix For: 4.2 -- 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

17 years, 7 months

1
2
0 / 0

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

esb-issues July 2007