Hi Jon,
Have you considered Castor?
Best regards,
Oleg
Jon Finanger wrote:
>> 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
JF> to
>> make every row in a database into an entity bean. The application won't
JF> scale well
>> this way.
JF> I can imagine NOT using entitybeans in the following cases:
JF> * When the data is read only data and/or need to get fast into the db
JF> (calling some sessionbean or inserting directly into the database)
JF> * When the client wants big resultsets to edit/display.
JF> But, if i retrieve a big resultset using a session bean i would use an
JF> entity bean in cases the client edits the row. Agree?
JF> Any other considerations of your experience?
JF> /Jon
JF> --
JF> --------------------------------------------------------------
JF> To subscribe: [EMAIL PROTECTED]
JF> To unsubscribe: [EMAIL PROTECTED]
JF> Problems?: [EMAIL PROTECTED]
--
--------------------------------------------------------------
To subscribe: [EMAIL PROTECTED]
To unsubscribe: [EMAIL PROTECTED]
Problems?: [EMAIL PROTECTED]
