Peter The ActiveDirectoryDAO that is generating the error isn't using Reactor at all. It uses custom functions that access the active directory data. I never should have posted that code it just lead to all kinds of misunderstandings.
I am hopeful that using getBean instead of createObject will solve my problem. I will report back on Monday (assuming I don't get sidetracked again at work). Bryan On 8/11/07, Peter J. Farrell <[EMAIL PROTECTED]> wrote: > > As for the DAO not working -- aren't Reactor beans self saving via the > active pattern? >
