At 18:10 19.02.00 , you wrote:
><snip>
>
> This must be a common enough usecase in J2EE programming that someone
> must
>have thought of this before, can anyone suggest a clean solution to this
>problem?
>
>
>thanks in advance,
>
>Floyd
you summed it up very nicely and there simply is no way of either avoiding
the database calls or the SQL join but what's wrong with that? entity beans
are a great tool for manipulating your datamodel and for RAD but when it
comes to presenting different views on the data (i.e. results of queries)
efficiently in most cases the best thing is to just write that sql.
encapsulate the query and the result in an object oriented way and make it
part of your facade. IMHO that's the most straight forward way to do it. I
try to avoid having to write sql and jdbc code where I can but you have to
be careful in deciding whether you're actually shooting yourself in the
foot by trying to avoid them at any cost. I have been using entity beans
(especially cmp) extensively in the past few months and I can now observe
the tendency to go back to the basics where it makes sense. why just use a
relational database as a dumb data bucket and not use its features?.
just my 2c
robert
(-) Robert Kr�ger
(-) SIGNAL 7 Gesellschaft f�r Informationstechnologie mbH
(-) Br�der-Knau�-Str. 79 - 64285 Darmstadt,
(-) Tel: 06151 665401, Fax: 06151 665373
(-) [EMAIL PROTECTED], www.signal7.de
===========================================================================
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".
