Hi Ed, > >in case you need to create new/update/remove existing records in db, you > >just use the CMP beans - call create() with your data or look it up using > >This goes against one of the most basic patterns in EJB design - allow >access to your entities only via session beans. Why is this recommended (accessing entity beans only through session beans)? For simple update, creation or deletion of a single record in the database that is mapped to an EJB entity, why would I want to go through a session bean instead of operating directly on the entity bean from my client code? Going through the session bean requires extra code (an additional method in a session bean), the extra overhead of two remote calls to pass the request through the session bean to the entity bean, and added complexity, with no real value as far as I can see. I can understand why one would want to encapsulate logic inside a session bean for use cases that update/create/delete more than 1 entity within a single transaction, but why do the same for an operation on a single entity bean? Thanks for your views, -------------------- Rick Horowitz _________________________________________________________ Do You Yahoo!? Get your free @yahoo.com address at http://mail.yahoo.com -- -------------------------------------------------------------- To subscribe: [EMAIL PROTECTED] To unsubscribe: [EMAIL PROTECTED] List Help?: [EMAIL PROTECTED]
