July 2007 - esb-issues - Jboss List Archives

[JBoss JIRA] Created: (JBESB-580) JMS synchronous replies are not correlated with request

by Kevin Conner (JIRA)

JMS synchronous replies are not correlated with request ------------------------------------------------------- Key: JBESB-580 URL: http://jira.jboss.com/jira/browse/JBESB-580 Project: JBoss ESB Issue Type: Bug Security Level: Public (Everyone can see) Reporter: Kevin Conner Assigned To: Kevin Conner Fix For: 4.2 JMS synchronous requests do not initialise a correlation ID for identifying responses. -- 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, 4 months

2
4
0 / 0

[JBoss JIRA] Reopened: (JBESB-297) Need for an SQL gateway that does not require altering 'legacy' data in any way

by Mark Little (JIRA)

[ http://jira.jboss.com/jira/browse/JBESB-297?page=all ] Mark Little reopened JBESB-297: ------------------------------- > Need for an SQL gateway that does not require altering 'legacy' data in any way > ------------------------------------------------------------------------------- > > Key: JBESB-297 > URL: http://jira.jboss.com/jira/browse/JBESB-297 > Project: JBoss ESB > Issue Type: Feature Request > Security Level: Public(Everyone can see) > Components: Rosetta > Affects Versions: 4.0 > Reporter: Esteban Schifman > Assigned To: Mark Little > Priority: Minor > Fix For: 4.2 Milestone Release 3 > > Original Estimate: 4 days > Remaining Estimate: 4 days > > Kurt has made a very valid point a couple of days ago regarding sql gateways. > Current SQL gateway requires an 'ad hoc' column in the watched table as an access indicator to avoid concurrency problems and repeated processing of the same event > Many legacy applications do not allow tampering with their data model, not even to have your own stored procedures in place, > We should try and find a way to have a version of the SqlTableListener that can work without the need to alter in any way (updating, deleting, adding stored procedures, etc.) the legacy database > This alternative would also allow to watch legacy 'views' (instead of simply db tables), thus broadening the scope of use of sql gateways. > Configuration will be somewhat more complex than our current sql gateway, but I think it's really worthwhile. -- 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, 4 months

1
0
0 / 0

[JBoss JIRA] Reopened: (JBESB-408) Implement an FtpNotifier

by Mark Little (JIRA)

[ http://jira.jboss.com/jira/browse/JBESB-408?page=all ] Mark Little reopened JBESB-408: ------------------------------- > Implement an FtpNotifier > ------------------------ > > Key: JBESB-408 > URL: http://jira.jboss.com/jira/browse/JBESB-408 > Project: JBoss ESB > Issue Type: Patch > Security Level: Public(Everyone can see) > Components: Rosetta > Affects Versions: 4.0 > Reporter: Rex Sheridan > Assigned To: Mark Little > Priority: Minor > Fix For: 4.2 > > Attachments: NotifyFTP.java > > > Currently there are notifiers for File, JMS, SQL, etc but none for FTP. This patch implements it. -- 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, 4 months

1
0
0 / 0

[JBoss JIRA] Closed: (JBESB-266) Improve structure of lib directory

by Mark Little (JIRA)

[ http://jira.jboss.com/jira/browse/JBESB-266?page=all ] Mark Little closed JBESB-266. ----------------------------- Fix Version/s: 4.2 Milestone Release 3 (was: 4.2) Resolution: Done > Improve structure of lib directory > ---------------------------------- > > Key: JBESB-266 > URL: http://jira.jboss.com/jira/browse/JBESB-266 > Project: JBoss ESB > Issue Type: Feature Request > Security Level: Public(Everyone can see) > Components: Packaging > Affects Versions: 4.0 Beta 1 Maintenance Pack 1 > Reporter: Mark Little > Assigned To: Mark Little > Fix For: 4.2 Milestone Release 3 > > > Restructure lib/ext into something like: > lib/build <--- jars needed to build the distribution but not run it > lib/core <--- jars needed to run the core ESB > lib/services/registry > lib/services/transformation > lib/services/persistence > Alternatively (and preferred), have the root lib only contain the build jars and have each submodule contain the jars needed to run it when built. -- 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, 4 months

1
0
0 / 0

[JBoss JIRA] Reopened: (JBESB-266) Improve structure of lib directory

by Mark Little (JIRA)

[ http://jira.jboss.com/jira/browse/JBESB-266?page=all ] Mark Little reopened JBESB-266: ------------------------------- > Improve structure of lib directory > ---------------------------------- > > Key: JBESB-266 > URL: http://jira.jboss.com/jira/browse/JBESB-266 > Project: JBoss ESB > Issue Type: Feature Request > Security Level: Public(Everyone can see) > Components: Packaging > Affects Versions: 4.0 Beta 1 Maintenance Pack 1 > Reporter: Mark Little > Assigned To: Mark Little > Fix For: 4.2 Milestone Release 3 > > > Restructure lib/ext into something like: > lib/build <--- jars needed to build the distribution but not run it > lib/core <--- jars needed to run the core ESB > lib/services/registry > lib/services/transformation > lib/services/persistence > Alternatively (and preferred), have the root lib only contain the build jars and have each submodule contain the jars needed to run it when built. -- 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, 4 months

1
0
0 / 0

[JBoss JIRA] Created: (JBESB-560) Store the original filename for messages originating on file or FTP gateways

by Derek Adams (JIRA)

Store the original filename for messages originating on file or FTP gateways ---------------------------------------------------------------------------- Key: JBESB-560 URL: http://jira.jboss.com/jira/browse/JBESB-560 Project: JBoss ESB Issue Type: Feature Request Security Level: Public (Everyone can see) Components: Transports Affects Versions: 4.2 Milestone Release 2 Reporter: Derek Adams Assigned To: Mark Little Priority: Minor Fix For: 4.2 When file and FTP gateways create messages to put on the bus, the original filename should be made available as part of the message. An example use-case for this would be polling a group of files on an FTP server at a given interval, doing some manipulation of the contents inside the ESB, then writing the message back out to FTP with the original file name plus a timestamp to make the file unique. -- 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, 4 months

2
7
0 / 0

[JBoss JIRA] Closed: (JBESB-297) Need for an SQL gateway that does not require altering 'legacy' data in any way

by Mark Little (JIRA)

[ http://jira.jboss.com/jira/browse/JBESB-297?page=all ] Mark Little closed JBESB-297. ----------------------------- Fix Version/s: 4.2 Milestone Release 3 (was: 4.2) Resolution: Rejected > Need for an SQL gateway that does not require altering 'legacy' data in any way > ------------------------------------------------------------------------------- > > Key: JBESB-297 > URL: http://jira.jboss.com/jira/browse/JBESB-297 > Project: JBoss ESB > Issue Type: Feature Request > Security Level: Public(Everyone can see) > Components: Rosetta > Affects Versions: 4.0 > Reporter: Esteban Schifman > Assigned To: Mark Little > Priority: Minor > Fix For: 4.2 Milestone Release 3 > > Original Estimate: 4 days > Remaining Estimate: 4 days > > Kurt has made a very valid point a couple of days ago regarding sql gateways. > Current SQL gateway requires an 'ad hoc' column in the watched table as an access indicator to avoid concurrency problems and repeated processing of the same event > Many legacy applications do not allow tampering with their data model, not even to have your own stored procedures in place, > We should try and find a way to have a version of the SqlTableListener that can work without the need to alter in any way (updating, deleting, adding stored procedures, etc.) the legacy database > This alternative would also allow to watch legacy 'views' (instead of simply db tables), thus broadening the scope of use of sql gateways. > Configuration will be somewhat more complex than our current sql gateway, but I think it's really worthwhile. -- 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, 4 months

1
0
0 / 0

[JBoss JIRA] Closed: (JBESB-297) Need for an SQL gateway that does not require altering 'legacy' data in any way

by Mark Little (JIRA)

[ http://jira.jboss.com/jira/browse/JBESB-297?page=all ] Mark Little closed JBESB-297. ----------------------------- Resolution: Rejected > Need for an SQL gateway that does not require altering 'legacy' data in any way > ------------------------------------------------------------------------------- > > Key: JBESB-297 > URL: http://jira.jboss.com/jira/browse/JBESB-297 > Project: JBoss ESB > Issue Type: Feature Request > Security Level: Public(Everyone can see) > Components: Rosetta > Affects Versions: 4.0 > Reporter: Esteban Schifman > Assigned To: Mark Little > Priority: Minor > Fix For: 4.2 > > Original Estimate: 4 days > Remaining Estimate: 4 days > > Kurt has made a very valid point a couple of days ago regarding sql gateways. > Current SQL gateway requires an 'ad hoc' column in the watched table as an access indicator to avoid concurrency problems and repeated processing of the same event > Many legacy applications do not allow tampering with their data model, not even to have your own stored procedures in place, > We should try and find a way to have a version of the SqlTableListener that can work without the need to alter in any way (updating, deleting, adding stored procedures, etc.) the legacy database > This alternative would also allow to watch legacy 'views' (instead of simply db tables), thus broadening the scope of use of sql gateways. > Configuration will be somewhat more complex than our current sql gateway, but I think it's really worthwhile. -- 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, 4 months

1
0
0 / 0

[JBoss JIRA] Reopened: (JBESB-297) Need for an SQL gateway that does not require altering 'legacy' data in any way

by Mark Little (JIRA)

[ http://jira.jboss.com/jira/browse/JBESB-297?page=all ] Mark Little reopened JBESB-297: ------------------------------- > Need for an SQL gateway that does not require altering 'legacy' data in any way > ------------------------------------------------------------------------------- > > Key: JBESB-297 > URL: http://jira.jboss.com/jira/browse/JBESB-297 > Project: JBoss ESB > Issue Type: Feature Request > Security Level: Public(Everyone can see) > Components: Rosetta > Affects Versions: 4.0 > Reporter: Esteban Schifman > Assigned To: Mark Little > Priority: Minor > Fix For: 4.2 Milestone Release 3 > > Original Estimate: 4 days > Remaining Estimate: 4 days > > Kurt has made a very valid point a couple of days ago regarding sql gateways. > Current SQL gateway requires an 'ad hoc' column in the watched table as an access indicator to avoid concurrency problems and repeated processing of the same event > Many legacy applications do not allow tampering with their data model, not even to have your own stored procedures in place, > We should try and find a way to have a version of the SqlTableListener that can work without the need to alter in any way (updating, deleting, adding stored procedures, etc.) the legacy database > This alternative would also allow to watch legacy 'views' (instead of simply db tables), thus broadening the scope of use of sql gateways. > Configuration will be somewhat more complex than our current sql gateway, but I think it's really worthwhile. -- 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, 4 months

1
0
0 / 0

[JBoss JIRA] Closed: (JBESB-70) Create separate Nagios plugin

by Mark Little (JIRA)

[ http://jira.jboss.com/jira/browse/JBESB-70?page=all ] Mark Little closed JBESB-70. ---------------------------- Fix Version/s: 4.2 Milestone Release 3 (was: 4.2) Resolution: Done > Create separate Nagios plugin > ----------------------------- > > Key: JBESB-70 > URL: http://jira.jboss.com/jira/browse/JBESB-70 > Project: JBoss ESB > Issue Type: Feature Request > Security Level: Public(Everyone can see) > Components: Management > Affects Versions: 4.0 Alpha 1 > Reporter: Mark Little > Assigned To: Mark Little > Priority: Optional > Fix For: 4.2 Milestone Release 3 > > > - common\src\org\jboss\soa\esb\util\NagiosStandaloneHeartbeat.java > 1) Refactor into a nagios specific plugin package? -- 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, 4 months

1
0
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

esb-issues July 2007