glassfish_at_javadesktop.org wrote:
> Currently, all work is performed is initiated from our EJB's. Every EJB has an @TransactionAttribute(TransactionAttributeType.REQUIRED)
>
> defined on the class, so every method should be transaction upon invocation.
>
> We are using Spring to manage our Dao layer and retrieve the data source from JNDI to inject into our Dao's. One possible issue that I might see is that I am not allowing Spring to acquire the TransacitonManager or UserTransaction from JNDI to allow the enlistment of the data source explicitly into the transaction that the container should have started at the EJB method invocation. Do you see this as a potential issue?
>
Yes, this has potential to cause these kind of exceptions.
regards
sankar
> [Message sent by forum member 'cmathrusse' (cmathrusse)]
>
> http://forums.java.net/jive/thread.jspa?messageID=290126
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: users-unsubscribe_at_glassfish.dev.java.net
> For additional commands, e-mail: users-help_at_glassfish.dev.java.net
>
>