Currently we are using JDBC for finders and EJB for creates and updates which is giving a very good performance compapred to CMP finders .
-----Original Message-----
From: Alok_Band [mailto:Alok_Band@(protected)]
Sent: Friday, September 19, 2003 11:26 AM
To: J2EEPATTERNS-INTEREST@(protected)
Subject: Re: Large finders on entity beans refactored
Still, there is overhead of constructing Remote Objects. Hence I think one
should use JDBC instead of EntityBean finder method.
Also one has better control over optmization of finder SQL query if JDBC is
used.
> -----Original Message-----
> From: Kalra, Ashwani [SMTP:ashwani.kalra@(protected)]
> Sent: Friday, September 19, 2003 11:25 AM
> To: J2EEPATTERNS-INTEREST@(protected)
> Subject: Re: Large finders on entity beans refactored
>
> This is exactly what I meant. Consider the case when I am executing a
> finder
> returning 1000 entities and then I discard them, doing nothing with them.
> Bringing them all in ready state and then putting them back in pool is
> too
> much overhead .
>
> >-----Original Message-----
> >From: Alok_Band [mailto:Alok_Band@(protected)]
> >Sent: Friday, September 19, 2003 11:12 AM
> >To: J2EEPATTERNS-INTEREST@(protected)
> >Subject: Re: Large finders on entity beans refactored
> >
> >
> >Please find in line.
> >
> >Regards,
> >Alok
> >
> >> -----Original Message-----
> >> From: Pradeep Kumar [SMTP:pradeepk@(protected)]
> >> Sent: Friday, September 19, 2003 10:48 AM
> >> To: J2EEPATTERNS-INTEREST@(protected)
> >> Subject: Re: Large finders on entity beans refactored
> >>
> >> -----Original Message-----
> >> From: Alok_Band [mailto:Alok_Band@(protected)]
> >> Sent: Friday, September 19, 2003 10:43 AM
> >> To: J2EEPATTERNS-INTEREST@(protected)
> >> Subject: Re: Large finders on entity beans refactored
> >>
> >> Container has to construct remote objects for all returned rows so
> >> container
> >> has to get all the identies (i.e. Primary Keys). And it is
> >linked with
> >> remote object by "EntityContext" which is sent to your Bean
> >class when it
> >> is
> >> associated with any EJB Object.
> >>
> >> SO THIS DOES MEAN THAT ALL THE OBJECTS MUST BE IN READY
> >STATE AND NOT IN
> >> POOLED STATE. RIGHT?
> > [Alok_Band] Entity Bean objects could be pooled. When they are
> >associated with any EJB object
> > then "EntityContext" would
> >reflect the identity
> >of the EJB object using "entityContext.getPrimaryKey()"
> > Say ur finder method returned some 25
> >rows, container would return ArrayList of 25 Remote interfaces.
> > At this point no entity bean could be ready
> >state. When client invokes any business method on any remote
> > Entity Bean object will associated with EJB
> >object on the server and it will go in ready state.
> >
> > Ofcourse algorithm when to
> >associated entity
> >bean objects with EJB Object could vary fron vendor to vendor.
> >>
> >>
> >>
> >> On the statement,
> >> "It doesnt give identity till there is request by client.
> >But there is
> >> cost
> >> of construction of Remote interfaces that it return to the client for
> >> multi
> >> object finders."
> >>
> >> From this I understand that Bean objects are not associated
> >with remote
> >> unless there request by client. But remote object do have associated
> >> "Identity" i.e. EntityContext.
> >>
> >> Thanks,
> >> Alok
> >>
> >>
> >> > -----Original Message-----
> >> > From: Pradeep Kumar [SMTP:pradeepk@(protected)]
> >> > Sent: Friday, September 19, 2003 9:58 AM
> >> > To: J2EEPATTERNS-INTEREST@(protected)
> >> > Subject: Re: Large finders on entity beans refactored
> >> >
> >> > To me the specs statement contradicts the behavior of the finder
> >> methods.
> >> > The very purpose of finding is to first get all the
> >identities (primary
> >> > keys), so now that you have the identities, how could the
> >container not
> >> > keep them in the ready state and loose the object
> >identities (pooled
> >> state
> >> > do not have any identities).
> >> >
> >> > I don't get it when you say that the identity is not given to the
> >> objects
> >> > until the client has requested. Where and how else the
> >identities are
> >> > maintained by the container?
> >> >
> >> > -----Original Message-----
> >> > From: Kalra, Ashwani [mailto:ashwani.kalra@(protected)]
> >> > Sent: Friday, September 19, 2003 9:54 AM
> >> > To: J2EEPATTERNS-INTEREST@(protected)
> >> > Subject: Re: Large finders on entity beans refactored
> >> >
> >> > Here is what specs says
> >> > "After the ejbFind<METHOD>(...) method completes, the
> >instance remains
> >> in
> >> > the pooled
> >> > state. The container may, but is not required to,
> >immediately activate
> >> the
> >> > objects that were
> >> > located by the finder using the transition through the
> >ejbActivate()
> >> > method. " Section 10.5.3 page no 177 of EJB 2.0
> >> >
> >> > It doesnt give identity till there is request by client.
> >But there is
> >> cost
> >> > of construction of Remote interfaces that it return to the
> >client for
> >> > multi object finders.
> >> > HTH
> >> > /Ashwani
> >> >
> >> >
> >> > -----Original Message-----
> >> > From: Pradeep Kumar [mailto:pradeepk@(protected)]
> >> > Sent: Friday, September 19, 2003 9:30 AM
> >> > To: J2EEPATTERNS-INTEREST@(protected)
> >> > Subject: Re: Large finders on entity beans refactored
> >> > While the container is executing the finder method, it must give
> >> > identities to each of the objects (primary keys). Hence,
> >they must be
> >> > placed in the ready state, since objects do not have any
> >identity in the
> >> > pooled state.
> >> >
> >> > Can someone please clarify the statement from the specs.
> >> >
> >> > -----Original Message-----
> >> > From: Kalra, Ashwani [mailto:ashwani.kalra@(protected)]
> >> > Sent: Thursday, September 18, 2003 7:28 PM
> >> > To: J2EEPATTERNS-INTEREST@(protected)
> >> > Subject: Re: Large finders on entity beans refactored
> >> >
> >> > 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)
> >> > 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.
> >> > ____________________________________________________
> >> > 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)
> >> >
> >====================================================================
> >> > 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)
> >> > 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.
> >> >
> >> > ____________________________________________________
> >> > 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)
> >> >
> >====================================================================
> >> > 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 email (including any attachments) is intended for the
> >sole use of the
> >> intended recipient/s and may contain material that is
> >CONFIDENTIAL AND
> >> PRIVATE COMPANY INFORMATION. Any review or reliance by
> >others or copying
> >> or
> >> distribution or forwarding of any or all of the contents in
> >this message
> >> is
> >> STRICTLY PROHIBITED. If you are not the intended recipient,
> >please contact
> >> the sender by email and delete all copies; your cooperation
> >in this regard
> >> is appreciated.
> >>
> >***************************************************************
> >***********
> >>
> >> ====================================================================
> >> 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)
> >>
> >>
> >> 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)
> >***************************************************************
> >***********
> >This email (including any attachments) is intended for the
> >sole use of the
> >intended recipient/s and may contain material that is CONFIDENTIAL AND
> >PRIVATE COMPANY INFORMATION. Any review or reliance by others
> >or copying or
> >distribution or forwarding of any or all of the contents in
> >this message is
> >STRICTLY PROHIBITED. If you are not the intended recipient,
> >please contact
> >the sender by email and delete all copies; your cooperation in
> >this regard
> >is appreciated.
> >***************************************************************
> >***********
> >
> >====================================================================
> >Companion Site: http://www.corej2eepatterns.com
> >J2EE BluePrints: http://java.sun.com/blueprints/corej2eepatterns
> >List Archive:
> >http://archives.java.sun.com/archives/j2eepatterns-interest.htm
> l
> 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)
**************************************************************************
This email (including any attachments) is intended for the sole use of the
intended recipient/s and may contain material that is CONFIDENTIAL AND
PRIVATE COMPANY INFORMATION. Any review or reliance by others or copying or
distribution or forwarding of any or all of the contents in this message is
STRICTLY PROHIBITED. If you are not the intended recipient, please contact
the sender by email and delete all copies; your cooperation in this regard
is appreciated.
**************************************************************************
====================================================================
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 e-mail and any files transmitted with it are for the sole use of the intended recipient(s) and may contain confidential and privileged information.
If you are not the intended recipient, please contact the sender by reply e-mail and destroy all copies of the original message.
Any unauthorised review, use, disclosure, dissemination, forwarding, printing or copying of this email or any action taken in reliance on this e-mail is strictly
prohibited and may be unlawful.
Visit us at http://www.cognizant.com
====================================================================
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)
