There is only good or bad design, no correct or incorrect ones. If your project is not using CMP and CRM, there is not much need for entity beans. But of course, a better design will use JDOs to encapsulate the database interaction part from business logic.
The second point, I have to say it's a more common approach. Usually, client side don't interact directly with entity beans, but route everything through session beans.
|