Tom Valesky wrote:
>
> Tim,
>
> That's basically my take on the situation as well (and I went through
> similar agonizing to
> arrive at the conclusion). Further, after you call findLargeAccounts(), you
> _still_ don't
> have what you really want -- you have to iterate over the set of references
> and coax
> the detail info out of each one. I found the
> query-in-the-wrapping-session-bean approach
> for getting aggregate info to be the most aesthetically pleasing.
>
But when you have CMP it is quite ugly, in my opinion, to go about and
use SQL queries on tables you do not manage, since you would like for
the container to manage the data storage fully transparently to the bean
provider. Of course I see the problem with providing a generic way to
define how such lightweight finder methods should be constructed (and
used). Still, it would be very, VERY nice to have them. I'm a sucker for
transparency and independence. =)
/Kalle
--
"Our wines leaves nothing to hope for." (What a restaurant)
Karl-Fredrik Blixt
Computer Science student at LiTH, Sweden
Homepage: http://o44.ryd.student.liu.se/
Telephone: +46-(0)13-47 39 206
Cellular: +46-(0)739-87 11 03
ICQ: 4744258
===========================================================================
To unsubscribe, send email to [EMAIL PROTECTED] and include in the body
of the message "signoff EJB-INTEREST". For general help, send email to
[EMAIL PROTECTED] and include in the body of the message "help".
