This content has been marked as final. Show 2 replies
It's logical that you can't read out any uncommitted data from a different transaction. So indeed, your solution lies in defining a transaction on the EJB method level, which would then be used for both the Tuxedo call as well as the JDBC step.
I haven't worked yet with Tuxedo, so I couldn't tell you whether it supports existing transaction.
They both are in the same transaction.