I would like professional advice on a good design pattern when using EJB3(session and entity). We have been having this debate at work about not using entity bean in the client and only allowing a session bean to access the entity beans. I had to take in my textbook(Beginning Java EE 5) to substantiate my claim that using the EB in the UI is not a good idea. However the decision has now went in favour of using common objects(previously EB) in the front end and passing them into the session bean which can then be marked with the @embeddable annotation and persisted by an entity bean? What are you're views and thoughts on this? What is a good design pattern to follow that will allow scalability as well as being quick to implement?
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3962607#3962607 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=3962607 _______________________________________________ jboss-user mailing list jboss-user@lists.jboss.org https://lists.jboss.org/mailman/listinfo/jboss-user
