[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
(was: 5.0)
Resolution: Rejected
We agreed that there was not enough call for this at this time. Can re-evaluate later if necessary.
> 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, 6 months
[JBoss JIRA] Assigned: (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 reassigned JBESB-297:
---------------------------------
Assignee: Mark Little (was: Esteban Schifman)
> 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: 5.0
>
> 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, 6 months