> > There can be no other solution, > > I thought I spoke to some vendor - maybe Persistence and they were handling > this by executing a finder - then checking their in-memory list and pushing > the list on top of what was retrieved from the database and reapplying the > query on those few in-memory beans pushed into the new list. Doesn't seem > very expensive or difficult - but then I'm probably being naive. OK, let's look at an example. I have a customer entity bean that uses bean managed persistence. I have a finder method, findAllCustomersWithBigNoses(). It takes no parameters and returns customers that meet a certain pre-defined criteria for having a big nose. Now, exactly how is the container supposed to iterate over all the customer entities in memory and determine which ones meet my finder method's criteria for having a big nose?
begin:vcard n:Wilson;Chip tel;fax:(214) 358-0353 tel;work:(214) 642-4559 x-mozilla-html:TRUE url:http://www.axyssolutions.com/ org:Axys Solutions adr:;;;Dallas;TX;; version:2.1 email;internet:[EMAIL PROTECTED] title:Application Architect note:Sun Certified Java Architect x-mozilla-cpt:;-25088 fn:Chip Wilson end:vcard
