  | Mailing List | | Home | | Forum Home | | JBoss - Java Application Server | | Struts - A MVC web framework | | Tomcat - JSP/Servlet container | | iText - An open source PDF Java Library | | JDOM - JDOM XML Parser | | J2EE - A mailing list for Java(tm) 2 Platform, Enterprise Edition | | J2EE Pattern - An interest list for Sun Java Center J2EE Pattern Catalog | | Servlet - A mailing list for discussion about Sun Microsystem's Java Servlet API Technology | | JSP - A mailing list about Java Server Pages specification and reference | |
Struts & Hibernate
|
|
|
  | | | Large finders on entity beans refactored | Large finders on entity beans refactored 2003-09-14 - By Katz Guy
Back Hi; 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?
__ ____ ____ ____ _____ Guy Katz Software Architect, CAP-IFS Comverse guy.katz@(protected) +972 3 7663686
==================================================================== 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@(protected)
<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 3.2//EN"> <HTML> <HEAD> <META HTTP-EQUIV="Content-Type" CONTENT="text/html; charset=windows-1255 (See http://ows-1255.ora-code.com)"> <META NAME="Generator" CONTENT="MS Exchange Server version 5.5.2655.35"> <TITLE>Large finders on entity beans refactored</TITLE> </HEAD> <BODY>
<P><FONT SIZE=2 FACE="Arial">Hi;</FONT> <BR><FONT SIZE=2 FACE="Arial">Going through the core patterns book.</FONT> <BR><FONT SIZE=2 FACE="Arial">There is a bad practice dedicated to not using finder methods when large result is expected but use a DAO instead.</FONT> <BR><FONT SIZE=2 FACE="Arial">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? </FONT></P>
<P><FONT SIZE=2 FACE="Arial">If so, wouldn't this be in contrast to resusability? Also, isnt this a good place to put your money on vendor container optimiations?</FONT></P>
<P><B><FONT SIZE=2 FACE="Arial">__ ____ ____ ____ _____</FONT></B> <BR><B><FONT SIZE=2 FACE="Arial">Guy Katz</FONT></B> <BR><B><FONT SIZE=2 FACE="Arial">Software Architect, CAP-IFS</FONT></B> <BR><B><FONT SIZE=2 FACE="Arial">Comverse</FONT></B> <BR><B><FONT SIZE=2 FACE="Arial">guy.katz@(protected)</FONT></B> <BR><B><FONT SIZE=2 FACE="Arial">+972 3 7663686</FONT></B> </P>
</BODY> </HTML> ==================================================================== 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@(protected)
|
|
 |