I was thinking the same thing. Just follow the Tomcat sample and pray it works!
Now this may be a semantic thing, but I always planned on a JPA based deployment--whether I went with EJB3 or POJOs. The plan was to use a persistence archive with Hibernate JPA hitting a datasource created on WL 9.2 and making that archive part of the larger deployment package (EAR or WAR). I was hoping to leverage EJB3 (or the reasonable facsimile provided by the embedded container) for management of session beans, transactions, managed persistence contexts, and all the other wondrous joys provided by the EJB3 spec. Not to mention that when and if my deployment environment (controlled by powers far outside my control) gets upgraded to WL 10 and certain EJB3 capability, then refactoring would be trivial. Does that clarify things? What did you mean by "JPA based deployment"? I have found the JPA vs. EJB3 entity beans discussion is always tricky. Also, just to be clear, are you saying I should pursue a POJO-based deployment as the existing WL 9.2 samples have rather than attempt the Tomcat-like EJB3 deployment? View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4092061#4092061 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4092061 _______________________________________________ jboss-user mailing list [email protected] https://lists.jboss.org/mailman/listinfo/jboss-user
