It sounds like it is time you move to the Spring Framework. [1] Do not allow your DAO to manage transactions.
[2] Transactions are managed by manager proxies. [3] Transaction Managers are configured to say which methods start a transaction. [4] Transaction Managers are smart enough to know, with your configuration, when to start a new transaction and when a method can run in an existing transaction. This way they can nest without a problem.... So I had the same problem you had. I had DAO's wanting to use each other, but this couldn't be done if they managed their own transactions internally. So I factored that code out, inserted the TM of Spring, and life is grand. Honestly, the architecture no longer supports your requirements; it's time for a change. If you need help, feel free to email me. Paul __________________________________________________ Do You Yahoo!? Tired of spam? Yahoo! Mail has the best spam protection around http://mail.yahoo.com --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
