> The specification is silent on the implications of saving a
> transactional resource such as a connection between business
> method calls. If it were legal for the container to make those
> resources non-transactional, this would certainly have been
> mentioned (EJB components using this pattern in transactional
> methods would not be portable). To me this implies that you must
> be able to re-enlist an existing, open connection into a new
> transaction.
I agree. And, as argued earlier, the only way to do this is to do tx->con
mapping in each Connection method invocation.
/Rickard
