Thanks as always Gavin. One more question if you don't mind. If I am using this
method, it begs the question why use session beans at all? POJOs would be
easier (no interface to maintain). Then the combination would be POJO + EJB3
entities. This pattern would be easier and yet still use EJB3 instead of
hibernate for persistence since that is more the "standard" now.
The question I have, is if an EntityManager can be used with POJOs?
@Name("pojo")
public class POJO {
@In(create=true)
private EntityManager entityManager;
View the original post :
http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3938157#3938157
Reply to the post :
http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=3938157
-------------------------------------------------------
Using Tomcat but need to do more? Need to support web services, security?
Get stuff done quickly with pre-integrated technology to make your job easier
Download IBM WebSphere Application Server v.1.0.1 based on Apache Geronimo
http://sel.as-us.falkag.net/sel?cmd=lnk&kid=120709&bid=263057&dat=121642
_______________________________________________
JBoss-user mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/jboss-user
