April 2007 - esb-issues - Jboss List Archives

[JBoss JIRA] Created: (JBESB-515) The standalone bootstrapper should close down the ESB using a shutdown hook

by Kevin Conner (JIRA)

The standalone bootstrapper should close down the ESB using a shutdown hook --------------------------------------------------------------------------- Key: JBESB-515 URL: http://jira.jboss.com/jira/browse/JBESB-515 Project: JBoss ESB Issue Type: Feature Request Security Level: Public (Everyone can see) Reporter: Kevin Conner Assigned To: Kevin Conner Fix For: 4.2 Milestone Release 2 The standalone bootstrapper will only shut down the ESB if it is allowed to terminate normally. It should use a shutdown hook so that it can catch other terminations. -- 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

19 years

1
3
0 / 0

[JBoss JIRA] Commented: (JBESB-417) Service lifecycle

by Kevin Conner (JIRA)

[ http://jira.jboss.com/jira/browse/JBESB-417?page=comments#action_12359824 ] Kevin Conner commented on JBESB-417: ------------------------------------ If the issues are covered by the other JIRA tasks then I believe we can drop the 4.2 requirements. I think this should stay open for 5 though. > Service lifecycle > ----------------- > > Key: JBESB-417 > URL: http://jira.jboss.com/jira/browse/JBESB-417 > Project: JBoss ESB > Issue Type: Task > Security Level: Public(Everyone can see) > Components: Management, Rosetta > Reporter: Mark Little > Assigned To: Kevin Conner > Fix For: 5.0 Milestone Release 1, 4.2 Milestone Release 2 > > > Both simple lifecycle on single bus as well as dev, test, staging, production management -- 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

19 years

1
0
0 / 0

[JBoss JIRA] Created: (JBESB-514) deployment.properties in 4.2 trunk

by Burr Sutter (JIRA)

deployment.properties in 4.2 trunk ---------------------------------- Key: JBESB-514 URL: http://jira.jboss.com/jira/browse/JBESB-514 Project: JBoss ESB Issue Type: Bug Security Level: Public (Everyone can see) Affects Versions: 4.2 Milestone Release 1 Reporter: Burr Sutter Assigned To: Mark Little Fix For: 4.2 Milestone Release 2 the property names in deployment.properties are no longer consistent with what is asked for in the build.xml org.jboss.esb.dist=../lib -> org.jboss.esb.dist .lib =../lib org.jboss.esb.appserver.config -> org.jboss.esb. server .config -- 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

19 years

4
7
0 / 0

[JBoss JIRA] Commented: (JBESB-436) More EIP

by Mark Little (JIRA)

[ http://jira.jboss.com/jira/browse/JBESB-436?page=comments#action_12359751 ] Mark Little commented on JBESB-436: ----------------------------------- 1) Wire Tap (based on static-router) http://www.enterpriseintegrationpatterns.com/WireTap.html 2) Message Filter (based on static-router or CBR with no exception handling) http://www.enterpriseintegrationpatterns.com/Filter.html 3) Receipt List (is kind of the static-router and can be renamed) http://www.enterpriseintegrationpatterns.com/RecipientList.html 4) Dynamic Router (based on CBR but allows for "feedback" from recipients) http://www.enterpriseintegrationpatterns.com/DynamicRouter.html 5) Claim Check and Message Store (how do we carry around the UID from Message Store) http://www.enterpriseintegrationpatterns.com/StoreInLibrary.html http://www.enterpriseintegrationpatterns.com/MessageStore.html 6) Process Manager (jBPM-based quickstart) http://www.enterpriseintegrationpatterns.com/eaipatterns.html 7) Resequencer (based on the aggregator) http://www.enterpriseintegrationpatterns.com/Resequencer.html 8) Normalizer is a quickstart sample (router + transformer/translator): http://www.enterpriseintegrationpatterns.com/Normalizer.html 9) Test Message (tracer concept) http://www.enterpriseintegrationpatterns.com/TestMessage.html 10) Content Enricher (Smooks, just document) http://www.enterpriseintegrationpatterns.com/DataEnricher.html This should handle lookup tables (db or just hashmaps) 11) Composed Message Router (a quickstart) http://www.enterpriseintegrationpatterns.com/DistributionAggregate.html > More EIP > -------- > > Key: JBESB-436 > URL: http://jira.jboss.com/jira/browse/JBESB-436 > Project: JBoss ESB > Issue Type: Feature Request > Security Level: Public(Everyone can see) > Components: Rosetta, Examples > 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

19 years

1
0
0 / 0

[JBoss JIRA] Closed: (JBESB-410) WS-BPEL support

by Tom Fennelly (JIRA)

[ http://jira.jboss.com/jira/browse/JBESB-410?page=all ] Tom Fennelly closed JBESB-410. ------------------------------ Resolution: Done Sure, I think there's enough there for now. We can add more tasks for whatever comes next. > WS-BPEL support > --------------- > > Key: JBESB-410 > URL: http://jira.jboss.com/jira/browse/JBESB-410 > Project: JBoss ESB > Issue Type: Feature Request > Security Level: Public(Everyone can see) > Components: BPM > Reporter: Mark Little > Assigned To: Tom Fennelly > Fix For: 4.2 Milestone Release 2 > > Time Spent: 2 weeks > Remaining Estimate: 0 minutes > > Adding BPEL support to the ESB, requires that all services have a configuration flag that dynamically renders WSDL from the current endpoint. -- 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

19 years

1
0
0 / 0

[JBoss JIRA] Commented: (JBESB-417) Service lifecycle

by Mark Little (JIRA)

[ http://jira.jboss.com/jira/browse/JBESB-417?page=comments#action_12359722 ] Mark Little commented on JBESB-417: ----------------------------------- Add a task for that and then we can close this one, right? > Service lifecycle > ----------------- > > Key: JBESB-417 > URL: http://jira.jboss.com/jira/browse/JBESB-417 > Project: JBoss ESB > Issue Type: Task > Security Level: Public(Everyone can see) > Components: Management, Rosetta > Reporter: Mark Little > Assigned To: Kevin Conner > Fix For: 5.0 Milestone Release 1, 4.2 Milestone Release 2 > > > Both simple lifecycle on single bus as well as dev, test, staging, production management -- 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

19 years

1
0
0 / 0

[JBoss JIRA] Commented: (JBESB-417) Service lifecycle

by Burr Sutter (JIRA)

[ http://jira.jboss.com/jira/browse/JBESB-417?page=comments#action_12359721 ] Burr Sutter commented on JBESB-417: ----------------------------------- I believe the specific situations are starting to be addressed by other Jira tasks such 507 439 438 There may be an adjustment needed to the lookup code so that it picks randomly from the list of EPRs returned. I'm not sure what logic is now. This will help with basic load-balancing and graceful undeployment should unregister its EPRs and they should no longer have traffic routed to them. This item likely needs its own Jira task. > Service lifecycle > ----------------- > > Key: JBESB-417 > URL: http://jira.jboss.com/jira/browse/JBESB-417 > Project: JBoss ESB > Issue Type: Task > Security Level: Public(Everyone can see) > Components: Management, Rosetta > Reporter: Mark Little > Assigned To: Kevin Conner > Fix For: 5.0 Milestone Release 1, 4.2 Milestone Release 2 > > > Both simple lifecycle on single bus as well as dev, test, staging, production management -- 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

19 years

1
0
0 / 0

[JBoss JIRA] Commented: (JBESB-410) WS-BPEL support

by Mark Little (JIRA)

[ http://jira.jboss.com/jira/browse/JBESB-410?page=comments#action_12359720 ] Mark Little commented on JBESB-410: ----------------------------------- Nice work Tom. Close this if it's done. > WS-BPEL support > --------------- > > Key: JBESB-410 > URL: http://jira.jboss.com/jira/browse/JBESB-410 > Project: JBoss ESB > Issue Type: Feature Request > Security Level: Public(Everyone can see) > Components: BPM > Reporter: Mark Little > Assigned To: Tom Fennelly > Fix For: 4.2 Milestone Release 2 > > Time Spent: 2 weeks > Remaining Estimate: 0 minutes > > Adding BPEL support to the ESB, requires that all services have a configuration flag that dynamically renders WSDL from the current endpoint. -- 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

19 years

1
0
0 / 0

[JBoss JIRA] Work logged: (JBESB-410) WS-BPEL support

by Tom Fennelly (JIRA)

[ http://jira.jboss.com/jira/browse/JBESB-410?page=worklog#action_12359719 ] Tom Fennelly logged work on JBESB-410: -------------------------------------- Time Spent: 1 week Time Spent: 2 weeks (was: 1 week) > WS-BPEL support > --------------- > > Key: JBESB-410 > URL: http://jira.jboss.com/jira/browse/JBESB-410 > Project: JBoss ESB > Issue Type: Feature Request > Security Level: Public(Everyone can see) > Components: BPM > Reporter: Mark Little > Assigned To: Tom Fennelly > Fix For: 4.2 Milestone Release 2 > > Time Spent: 2 weeks > Remaining Estimate: 0 minutes > > Adding BPEL support to the ESB, requires that all services have a configuration flag that dynamically renders WSDL from the current endpoint. -- 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

19 years

1
0
0 / 0

[JBoss JIRA] Work logged: (JBESB-410) WS-BPEL support

by Tom Fennelly (JIRA)

[ http://jira.jboss.com/jira/browse/JBESB-410?page=worklog#action_12359718 ] Tom Fennelly logged work on JBESB-410: -------------------------------------- Time Spent: 1 week Remaining Estimate: 0 minutes Time Spent: 1 week > WS-BPEL support > --------------- > > Key: JBESB-410 > URL: http://jira.jboss.com/jira/browse/JBESB-410 > Project: JBoss ESB > Issue Type: Feature Request > Security Level: Public(Everyone can see) > Components: BPM > Reporter: Mark Little > Assigned To: Tom Fennelly > Fix For: 4.2 Milestone Release 2 > > Time Spent: 1 week > Remaining Estimate: 0 minutes > > Adding BPEL support to the ESB, requires that all services have a configuration flag that dynamically renders WSDL from the current endpoint. -- 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

19 years

1
0
0 / 0

2026

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

esb-issues April 2007