Hi, I am reading someone's code. I find that he has implemented all the insert / update / delete functions within stored procedure and query operations within Entity Bean. To the best of the my knowledge, I feel that this implementation is not exploiting EJB features properly. I feel EJB provide tranasction services. Implementation should be done as: 1. All the inserts / update / deletes should be implemented using Entity bean. 2. Complex Retrieve should be implemented using views and creating beans over these views. Before commenting over anyone's code, I thought I will discuss within group member about their views. Can you please provide me your feedback on the same? Regards, Chetan Mehta
I'm with you. This isn't right. It's exactly the opposite of what I usually do -- which is implement set/update functionality in Entity beans, and then do "large result set" queries using Stored procedures, Value Objects and Stateless Session beans... Kyle ------------------ Kyle Brown, Author of Enterprise Java (tm) Programming with IBM Websphere See my homepage at http://members.aol.com/kgb1001001 for other WebSphere information.