Sorry forgot this link last time - check out -
http://www.netnumina.com/content/technology/enterprise_ejbs.html
That's what I'm really thinking...
Cheers
Jay Walters
-----Original Message-----
From: Jay Walters [mailto:[EMAIL PROTECTED]]
Sent: Wednesday, November 22, 2000 12:33 PM
To: 'jBoss'
Subject: RE: [jBoss-User] Any R-O tool's out there?
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.
Cheers
-----Original Message-----
From: Jon Finanger [mailto:[EMAIL PROTECTED]]
Sent: Wednesday, November 22, 2000 7:53 AM
To: jBoss
Subject: RE: [jBoss-User] Any R-O tool's out there?
> 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]
--
--------------------------------------------------------------
To subscribe: [EMAIL PROTECTED]
To unsubscribe: [EMAIL PROTECTED]
Problems?: [EMAIL PROTECTED]
--
--------------------------------------------------------------
To subscribe: [EMAIL PROTECTED]
To unsubscribe: [EMAIL PROTECTED]
Problems?: [EMAIL PROTECTED]
