Along those lines, I've added an entry to the iBatis Wiki (http://wiki.apache.org/ibatis/). Select "3rd Party Contributions" and review the section "Convert ResultSet to JSTL Result". You can think of JSTL's Result interface as something *similar* to JDBC's CachedRowSet and BeanUtils' RowSetDynaClass. The example is slanted towards handling cursors that are output parameters from stored procedures, but the basic idea can applied anywhere you want to extract data from a ResultSet.
Quoting Joe Hertz <[EMAIL PROTECTED]>: > Vic writes: > > > :snip: > > The point is... I use ArrayList of Maps now for my DTO,VO and ever as a > > message object for WS/SOA. > > > > Wherever I used to use a bean, now I use a collection, and I like > > DynaMaps. > > > > maybe one day you guys catch up;-) > > I think I'm buying what you say in a big kinda way. I've been there already > I think, but forcing myself to use the DynaBean route and if you've read my > posts here, you know I'm frustrated. I've been coming to your conclusion, > and I'd love to hear more from you offline if you don't mind. > > I disagree vehemently that the idea of Maps in the Domain Model is a bad > design. I worked for years in an architecture that eschewed many OO concepts > as creating more work than they saved. > > Its universe was something like this- > > A Database contains a map of Table Objects > A Table object contains an array list of Record Objects. > A Record object contains a map of Field Objects. > Etc > > Done properly, something like this could be infinitely reusable no matter > what the application. -- Kris Schneider <mailto:[EMAIL PROTECTED]> D.O.Tech <http://www.dotech.com/> --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
