August 2007 - esb-issues - Jboss List Archives

[JBoss JIRA] Created: (JBESB-826) Scheduled deployments and versioned deployments

by Kurt Stam (JIRA)

Scheduled deployments and versioned deployments ----------------------------------------------- Key: JBESB-826 URL: http://jira.jboss.com/jira/browse/JBESB-826 Project: JBoss ESB Issue Type: Feature Request Security Level: Public (Everyone can see) Reporter: Kurt Stam Assigned To: Mark Little Fix For: 5.0 Not only hot, but - Scheduled: e.g. 'deploy now' become active at 23:00 (or 11pm ;-) ), or mark a service as becomming unavailable a 3 weeks from now - Versioned: Service A version 1 uses Service B version 2, Service B gets a new version, needed for other things, but Service A should still be able to use Service B version 2 for as long as needed. -- 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

18 years, 8 months

2
2
0 / 0

[JBoss JIRA] Closed: (JBESB-431) Hot redeployment

by Kurt Stam (JIRA)

[ http://jira.jboss.com/jira/browse/JBESB-431?page=all ] Kurt Stam closed JBESB-431. --------------------------- Fix Version/s: (was: 5.0 Milestone Release 1) Resolution: Done "Action classes, DRLs, process def scripts, transformation selection rules." This is implemented for 4.2. I'm opening a new issue for the scheduled and version deployments > Hot redeployment > ---------------- > > Key: JBESB-431 > URL: http://jira.jboss.com/jira/browse/JBESB-431 > Project: JBoss ESB > Issue Type: Feature Request > Security Level: Public(Everyone can see) > Components: Rosetta, Configuration, Management > Reporter: Mark Little > Assigned To: Kurt Stam > Fix For: 4.2 > > > Action classes, DRLs, process def scripts, transformation selection rules. -- 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

18 years, 8 months

1
0
0 / 0

[JBoss JIRA] Created: (JBESB-576) Hot redeployment documentation

by Mark Little (JIRA)

Hot redeployment documentation ------------------------------ Key: JBESB-576 URL: http://jira.jboss.com/jira/browse/JBESB-576 Project: JBoss ESB Issue Type: Task Security Level: Public (Everyone can see) Components: Documentation Reporter: Mark Little Assigned To: Kevin Conner Priority: Critical Fix For: 4.2 Make sure our docs on hot redeployment are sufficient. -- 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

18 years, 8 months

3
4
0 / 0

[JBoss JIRA] Created: (JBESB-462) Oracle AQ JMS Provider

by Burr Sutter (JIRA)

Oracle AQ JMS Provider ---------------------- Key: JBESB-462 URL: http://jira.jboss.com/jira/browse/JBESB-462 Project: JBoss ESB Issue Type: Feature Request Security Level: Public (Everyone can see) Components: Rosetta Reporter: Burr Sutter Assigned To: Mark Little Fix For: 4.2 JBoss ESB needs to be tested with Oracle AQ as the JMS provider implementation. -- 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

18 years, 8 months

3
8
0 / 0

[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

18 years, 8 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

18 years, 8 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

18 years, 8 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

18 years, 8 months

3
4
0 / 0

[JBoss JIRA] Created: (JBESB-821) remove IDE setup doc

by Kurt Stam (JIRA)

remove IDE setup doc -------------------- Key: JBESB-821 URL: http://jira.jboss.com/jira/browse/JBESB-821 Project: JBoss ESB Issue Type: Bug Security Level: Public (Everyone can see) Components: Documentation Affects Versions: 4.2 Milestone Release 3 Reporter: Kurt Stam Assigned To: Kurt Stam Fix For: 4.2 remove ide setup doc -- 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

18 years, 8 months

1
1
0 / 0

[JBoss JIRA] Created: (JBESB-809) Programmers Guide: Remove Old jboss-esb.xml action config syntax (page 49)

by Burr Sutter (JIRA)

Programmers Guide: Remove Old jboss-esb.xml action config syntax (page 49) -------------------------------------------------------------------------- Key: JBESB-809 URL: http://jira.jboss.com/jira/browse/JBESB-809 Project: JBoss ESB Issue Type: Bug Security Level: Public (Everyone can see) Components: Documentation Affects Versions: 4.2 Milestone Release 3 Reporter: Burr Sutter Assigned To: Mark Little Priority: Critical Fix For: 4.2 Clean up Programmers Guide to use proper (as exhibited by the quickstarts) jboss-esb.xml configuration of listeners, actions, services, etc. -- 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

18 years, 8 months

3
3
0 / 0

2026

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

esb-issues August 2007