> Sorry, I didn't mean to not use entity beans, what I mean is to not model
> each row in the database as an entity bean. Something like if I have an
> invoice with 10 line items I'd like to model the invoice as an entity bean
> and the line items as dependent objects within the invoice vs modeling all
> 11 rows as separate entity beans.
Weel, i see your point... The entity bean will the be a bit more coarse
grained and maybe have some rules combined to it.
Anyhow, i would think that a session bean wrapping the invoice entity and
the invoiceline entity would also work just as well.
Perfomance problems could of course be a reason to choose your approach -
which should be more efficient.
/Jon
--
--------------------------------------------------------------
To subscribe: [EMAIL PROTECTED]
To unsubscribe: [EMAIL PROTECTED]
Problems?: [EMAIL PROTECTED]
