==================================================================== Companion Site: http://www.corej2eepatterns.com J2EE BluePrints: http://java.sun.com/blueprints/corej2eepatterns List Archive: http://archives.java.sun.com/archives/j2eepatterns-interest.html Unsubscribing: email "signoff J2EEPATTERNS-INTEREST" to listserv@java.sun.com-----Original Message-----
From: Katz Guy [mailto:Guy_Katz@ICOMVERSE.COM]
Sent: Sunday, September 14, 2003 1:42 AM
To: J2EEPATTERNS-INTEREST@JAVA.SUN.COM
Subject: Large finders on entity beans refactoredHi;
Going through the core patterns book.
There is a bad practice dedicated to not using finder methods when large result is expected but use a DAO instead.
My understanding is that the authors want to have a 'dual interface' for access to the same data, Modeling the data itself as entity beans yet using DAO for the search. Is this correct?If so, wouldn't this be in contrast to resusability? Also, isnt this a good place to put your money on vendor container optimiations?
_______________________
==================================================================== Companion Site: http://www.corej2eepatterns.com J2EE BluePrints: http://java.sun.com/blueprints/corej2eepatterns List Archive: http://archives.java.sun.com/archives/j2eepatterns-interest.html Unsubscribing: email "signoff J2EEPATTERNS-INTEREST" to listserv@java.sun.com
Guy Katz
Software Architect, CAP-IFS
Comverse
guy.katz@comverse.com
+972 3 7663686