 | 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-18 - By Kalra, Ashwani
Back
Here what I read from specs 2.0
"The instance does not move to the ready state during the execution of a
finder or a home
method."
-- --Original Message-- --
From: Pradeep Kumar [mailto:pradeepk@(protected)]
Sent: Monday, September 15, 2003 9:54 AM
To: J2EEPATTERNS-INTEREST@(protected)
Subject: Re: Large finders on entity beans refactored
I totally agree. We are told that if we read a large amt of data via entity
beans, there will be too many entity objects in ready state. One can argue,
that they will be the cached data for subsequent reads (lets? say via find
by primary key), however, to avoid dirty reads, the container calls the EJB
load method, which defeats the purpose of caching
-- --Original Message-- --
From: Katz Guy [mailto:Guy_Katz@(protected)]
Sent: Sunday, September 14, 2003 12:12 PM
To: J2EEPATTERNS-INTEREST@(protected)
Subject: Large finders on entity beans refactored
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
DISCLAIMER:
This message (including attachment if any) is confidential and may be
privileged. Before opening attachments please check them for viruses and
defects. MindTree Consulting Private Limited (MindTree) will not be
responsible for any viruses or defects or any forwarded attachments
emanating either from within MindTree or outside. If you have received this
message by mistake please notify the sender by return e-mail and delete this
message from your system. Any unauthorized use or dissemination of this
message in whole or in part is strictly prohibited. Please note that e-mails
are susceptible to change and MindTree shall not be liable for any improper,
untimely or incomplete transmission.
====================================================================
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)
====================================================================
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)
__ ____ ____ ____ ____ ____ ____ ____ ____ ____ ____
This message contains information that may be privileged or confidential and
is the property of the Cap Gemini Ernst & Young Group. It is intended only
for the person to whom it is addressed. If you are not the intended
recipient, you are not authorised to read, print, retain, copy, disseminate,
distribute, or use this message or any part thereof. If you receive this
message in error, please notify the sender immediately and delete all copies
of this message.
====================================================================
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 4.0 Transitional//EN">
<HTML xmlns="http://www.w3.org/TR/REC-html40" xmlns:o =
"urn:schemas-microsoft-com:office:office" xmlns:w =
"urn:schemas-microsoft-com:office:word"><HEAD>
<META HTTP-EQUIV="Content-Type" CONTENT="text/html; charset=windows-1255 (See http://ows-1255.ora-code.com)">
<TITLE>Large finders on entity beans refactored</TITLE>
<META content=Word.Document name=ProgId>
<META content="MSHTML 5.50.4134.600" name=GENERATOR>
<META content="Microsoft Word 9" name=Originator><LINK
href="cid:filelist.xml@(protected)" rel=File-List><!--[if gte mso 9]><xml>
<o:OfficeDocumentSettings>
<o:DoNotRelyOnCSS/>
</o:OfficeDocumentSettings>
</xml><![endif]--><!--[if gte mso 9]><xml>
<w:WordDocument>
<w:Zoom>0</w:Zoom>
<w:DocumentKind>DocumentEmail</w:DocumentKind>
<w:EnvelopeVis/>
</w:WordDocument>
</xml><![endif]-->
<STYLE>@(protected) {
font-family: Tahoma;
}
@(protected) Section1 {size: 8.5in 11.0in; margin: 1.0in 1.25in 1.0in 1.25in; mso
-header-margin: .5in; mso-footer-margin: .5in; mso-paper-source: 0; }
P.MsoNormal {
FONT-SIZE: 12pt; MARGIN: 0in 0in 0pt; FONT-FAMILY: "Times New Roman";
mso-style-parent: ""; mso-pagination: widow-orphan; mso-fareast-font-family:
"Times New Roman"; mso-bidi-language: HE
}
LI.MsoNormal {
FONT-SIZE: 12pt; MARGIN: 0in 0in 0pt; FONT-FAMILY: "Times New Roman";
mso-style-parent: ""; mso-pagination: widow-orphan; mso-fareast-font-family:
"Times New Roman"; mso-bidi-language: HE
}
DIV.MsoNormal {
FONT-SIZE: 12pt; MARGIN: 0in 0in 0pt; FONT-FAMILY: "Times New Roman";
mso-style-parent: ""; mso-pagination: widow-orphan; mso-fareast-font-family:
"Times New Roman"; mso-bidi-language: HE
}
P.MsoAutoSig {
FONT-SIZE: 12pt; MARGIN: 0in 0in 0pt; FONT-FAMILY: "Times New Roman";
mso-pagination: widow-orphan; mso-fareast-font-family: "Times New Roman"; mso
-bidi-language: HE
}
LI.MsoAutoSig {
FONT-SIZE: 12pt; MARGIN: 0in 0in 0pt; FONT-FAMILY: "Times New Roman";
mso-pagination: widow-orphan; mso-fareast-font-family: "Times New Roman"; mso
-bidi-language: HE
}
DIV.MsoAutoSig {
FONT-SIZE: 12pt; MARGIN: 0in 0in 0pt; FONT-FAMILY: "Times New Roman";
mso-pagination: widow-orphan; mso-fareast-font-family: "Times New Roman"; mso
-bidi-language: HE
}
P {
FONT-SIZE: 12pt; MARGIN-LEFT: 0in; MARGIN-RIGHT: 0in; FONT-FAMILY:
"Times New Roman"; mso-pagination: widow-orphan; mso-fareast-font-family: "Times
New Roman"; mso-bidi-language: HE; mso-margin-top-alt: auto; mso-margin-bottom
-alt: auto
}
SPAN.EmailStyle16 {
COLOR: navy; mso-style-type: personal-reply; mso-ansi-font-size: 10.0pt
; mso-ascii-font-family: Arial; mso-hansi-font-family: Arial; mso-bidi-font
-family: Arial
}
DIV.Section1 {
page: Section1
}
</STYLE>
</HEAD>
<BODY lang=EN-US style="tab-interval: .5in">
<DIV><SPAN class=718175313-18092003><FONT color=#0000ff size=2>Here what I read
from specs 2.0</FONT></SPAN></DIV>
<DIV><SPAN class=718175313-18092003><FONT color=#0000ff
size=2></FONT></SPAN> </DIV>
<DIV><SPAN class=718175313-18092003><FONT color=#0000ff size=2>"The instance
does not move to the ready state during the execution of a finder or a
home<BR>method."</FONT></SPAN></DIV>
<BLOCKQUOTE dir=ltr
style="PADDING-LEFT: 5px; MARGIN-LEFT: 5px; BORDER-LEFT: #0000ff 2px solid;
MARGIN-RIGHT: 0px">
<DIV class=OutlookMessageHeader dir=ltr align=left><FONT face=Tahoma
size=2>-- --Original Message-- --<BR><B>From:</B> Pradeep Kumar
[mailto:pradeepk@(protected)]<BR><B>Sent:</B> Monday, September 15, 2003 9
:54
AM<BR><B>To:</B> J2EEPATTERNS-INTEREST@(protected)<BR><B>Subject:</B> Re:
Large finders on entity beans refactored<BR><BR></FONT></DIV>
<DIV class=Section1>
<P class=MsoNormal><SPAN class=EmailStyle16><FONT face=Arial color=navy
size=2><SPAN
style="FONT-SIZE: 10pt; FONT-FAMILY: Arial; mso-bidi-font-size: 12.0pt">I
totally agree. We are told that if we read a large amt of data via entity
beans, there will be too many entity objects in ready state. One can argue,
that they will be the cached data for subsequent reads (lets? say via find by
primary key), however, to avoid dirty reads, the container calls the EJB load
method, which defeats the purpose of
caching<o:p></o:p></SPAN></FONT></SPAN></P>
<P class=MsoNormal><SPAN class=EmailStyle16><FONT face=Arial color=navy
size=2><SPAN
style="FONT-SIZE: 10pt; FONT-FAMILY: Arial; mso-bidi-font-size: 12.0pt"><![if
!supportEmptyParas]><![endif]> <o:p></o:p></SPAN></FONT></SPAN></P>
<P class=MsoNormal style="MARGIN-LEFT: 0.5in"><FONT face=Tahoma color=black
size=2><SPAN
style="FONT-SIZE: 10pt; COLOR: black; FONT-FAMILY: Tahoma">-- --Original
Message-- --<BR><B><SPAN style="FONT-WEIGHT: bold">From:</SPAN></B> Katz Guy
[mailto:Guy_Katz@(protected)]<BR><B><SPAN
style="FONT-WEIGHT: bold">Sent:</SPAN></B> Sunday, September 14, 2003 12:12
PM<BR><B><SPAN style="FONT-WEIGHT: bold">To:</SPAN></B>
J2EEPATTERNS-INTEREST@(protected)<BR><B><SPAN
style="FONT-WEIGHT: bold">Subject:</SPAN></B> Large finders on entity beans
refactored</SPAN></FONT></P>
<P class=MsoNormal style="MARGIN-LEFT: 0.5in"><FONT face="Times New Roman"
size=3><SPAN
style="FONT-SIZE: 12pt"><![if !supportEmptyParas]><![endif]> <o:p></o:p>
</SPAN></FONT></P>
<P style="MARGIN-LEFT: 0.5in"><FONT face=Arial color=black size=2><SPAN
style="FONT-SIZE: 10pt; COLOR: black; FONT-FAMILY: Arial">Hi;</SPAN></FONT>
<FONT
color=black><SPAN style="COLOR: black"> <BR></SPAN></FONT><FONT face=Arial
color=black size=2><SPAN
style="FONT-SIZE: 10pt; COLOR: black; FONT-FAMILY: Arial">Going through the
core patterns book.</SPAN></FONT><FONT color=black><SPAN style="COLOR: black"
>
<BR></SPAN></FONT><FONT face=Arial color=black size=2><SPAN
style="FONT-SIZE: 10pt; COLOR: black; FONT-FAMILY: Arial">There is a bad
practice dedicated to not using finder methods when large result is expected
but use a DAO instead.</SPAN></FONT><FONT color=black><SPAN
style="COLOR: black"> <BR></SPAN></FONT><FONT face=Arial color=black
size=2><SPAN style="FONT-SIZE: 10pt; COLOR: black; FONT-FAMILY: 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? </SPAN></FONT><FONT color=black><SPAN
style="COLOR: black; mso-color-alt: windowtext"><o:p></o:p></SPAN></FONT></P>
<P style="MARGIN-LEFT: 0.5in"><FONT face=Arial color=black size=2><SPAN
style="FONT-SIZE: 10pt; COLOR: black; FONT-FAMILY: 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?</SPAN></FONT><FONT color=black><SPAN
style="COLOR: black; mso-color-alt: windowtext"><o:p></o:p></SPAN></FONT></P>
<P style="MARGIN-LEFT: 0.5in"><B><FONT face=Arial color=black size=2><SPAN
style="FONT-WEIGHT: bold; FONT-SIZE: 10pt; COLOR: black; FONT-FAMILY: Arial">
__ ____ ____ ____ _____</SPAN></FONT></B><FONT
color=black><SPAN style="COLOR: black"> <BR></SPAN></FONT><B><FONT face=Arial
color=black size=2><SPAN
style="FONT-WEIGHT: bold; FONT-SIZE: 10pt; COLOR: black; FONT-FAMILY: Arial"
>Guy
Katz</SPAN></FONT></B><FONT color=black><SPAN style="COLOR: black">
<BR></SPAN></FONT><B><FONT face=Arial color=black size=2><SPAN
style="FONT-WEIGHT: bold; FONT-SIZE: 10pt; COLOR: black; FONT-FAMILY: Arial"
>Software
Architect, CAP-IFS</SPAN></FONT></B><FONT color=black><SPAN
style="COLOR: black"> <BR></SPAN></FONT><B><FONT face=Arial color=black
size=2><SPAN
style="FONT-WEIGHT: bold; FONT-SIZE: 10pt; COLOR: black; FONT-FAMILY: Arial"
>Comverse</SPAN></FONT></B><FONT
color=black><SPAN style="COLOR: black"> <BR></SPAN></FONT><B><FONT face=Arial
color=black size=2><SPAN
style="FONT-WEIGHT: bold; FONT-SIZE: 10pt; COLOR: black; FONT-FAMILY: Arial"
>guy.katz@(protected)</SPAN></FONT></B><FONT
color=black><SPAN style="COLOR: black"> <BR></SPAN></FONT><B><FONT face=Arial
color=black size=2><SPAN
style="FONT-WEIGHT: bold; FONT-SIZE: 10pt; COLOR: black; FONT-FAMILY: Arial">
+972
3 7663686</SPAN></FONT></B><FONT color=black><SPAN style="COLOR: black">
</SPAN></FONT><FONT color=black><SPAN
style="COLOR: black; mso-color-alt: windowtext"><o:p></o:p></SPAN></FONT></P>
</DIV>
<P></P>
<P>DISCLAIMER:<BR>This message (including attachment if any) is confidential
and may be privileged. Before opening attachments please check them for
viruses and defects. MindTree Consulting Private Limited (MindTree) will not
be responsible for any viruses or defects or any forwarded attachments
emanating either from within MindTree or outside. If you have received this
message by mistake please notify the sender by return e-mail and delete this
message from your system. Any unauthorized use or dissemination of this
message in whole or in part is strictly prohibited. Please note that e-mails
are susceptible to change and MindTree shall not be liable for any improper,
untimely or incomplete transmission.
====================================================================
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)
====================================================================
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)</P></BLOCKQUOTE></BODY></HTML>
<BR>
<P><B><FONT SIZE=2 FACE="Arial">__ ____ ____ ____ ____ ____ ____ ____ ____ ____
__ __</FONT></B></P>
<P><B><FONT SIZE=2 FACE="Arial">This message contains information that may be
privileged or confidential and is the property of the Cap Gemini Ernst & Young
Group. It is intended only for the person to whom it is addressed. If you are
not the intended recipient, you are not authorised to read, print, retain, copy
, disseminate, distribute, or use this message or any part thereof. If you
receive this message in error, please notify the sender immediately and delete
all copies of this message.</FONT></B></P>
====================================================================
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)
|
|
|
