This question is ejb related, in the since that ejb defines the concept of
"entity beans". However, I am more interested in the idea of "entity
classes" generally. By Entity Class, I mean a class that mirrors (or
abstracts) a record in the database. But not necessarily an EJB Entity Bean.
I have a friend who does VB/database programming for a living. He is very
good and his customers like his work very much. However, he doesn't really
use classes that mirror his database tables. (Yes, VB does have classes). He
pretty much puts all of his code in the VB Form. This code, then, directly
performs SQL statements against the database. His position is that entity
classes, just add extra unneeded layer.
Some people, on the other hand, like to create classes (like Company,
Person, Invoice) that model the database entities, and have those classes
hide (or abstract) the database from the VB Form.
So my question is this: Are people, outside of EJB, generally using entity
classes? Are entity classes more pain than their worth? Does CMP make them
less of a pain?
Dave
===========================================================================
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".
