I can't really control this (or create a singleton) since Avalon/Phoenix is
instantiating the objects. I guess I'll have to go through that code and
figure out what's going wrong.
On the bright side, the JDBC repository is working other than that. I think
I have a bug or two to squash, and want to test a mixture of repositories
(like spool repository as JDBC and outgoing repository as file).
Serge Knystautas
Loki Technologies
http://www.lokitech.com/
----- Original Message -----
From: "Harmeet" <[EMAIL PROTECTED]>
> You should not be getting 2 separate instances of JDBC Repository. I think
> that is the key.
> My impression(don't fully remember the code) is that the logic is
> wait-notify so 2 repositories would be bad. (the wait-notify could be bad,
> because it assumes same process)
> You could try making the JDBC Repository a singleton and see if that fixes
> the problem.
>
> Harmeet
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
