On 7/26/06, Gary VanMatre <[EMAIL PROTECTED]> wrote:
I hate the idea of creating more layers. The extra setter methods for the entity manager on the session bean sounds much simpler. I'm not sure how the transaction would be handled transparently for in container versus out of container? The examples that I have seen, uses the JNDI UserTransaction in container and the EntityTransaction out of container.
FWIW, the mailreader-jpa persistence unit that is currently checked in uses resource local transactions, even inside the container. I like the idea of using the same transaction apis inside and outside ... and I also like the fact that EntityTransaction has an isActive() method, plus it throws unchecked exceptions like all the other JPA APIs. Craig
