> I can see why you would want the tool to map a relational schema
> onto entity beans and dependent objects, but I don't think you really want
to
> make every row in a database into an entity bean. The application won't
scale well
> this way.
I can imagine NOT using entitybeans in the following cases:
* When the data is read only data and/or need to get fast into the db
(calling some sessionbean or inserting directly into the database)
* When the client wants big resultsets to edit/display.
But, if i retrieve a big resultset using a session bean i would use an
entity bean in cases the client edits the row. Agree?
Any other considerations of your experience?
/Jon
--
--------------------------------------------------------------
To subscribe: [EMAIL PROTECTED]
To unsubscribe: [EMAIL PROTECTED]
Problems?: [EMAIL PROTECTED]
