Hi
Ok, thanks a lot. I'll look into it.
The reason I care about it it's because I was thinking of using a
ExecutorService (and the JDK 5.0 concurrent classes) instead of instancing
and managing by hand all the waiting threads.
regards,
Rafa
Stefano Bagnara-2 wrote:
>
> rafael.munoz ha scritto:
>> Hi
>>
>> Sorry to bother you again (I guess you are now thinking to answer me with
>> a
>> 'oh, please, shut up' ;) ) but I just can't find it on the
>> AvalonMailRepository (the one I'm using) or in any of the other
>> MailRepository or SpoolRepository implementations. Can you point me out
>> to
>> the exact code that implement the feature?
>>
>> In fact, I don't exactly understand how the spool is going to know about
>> the
>> waiting threads that are own and manage by the RemoteDelivery mailet.
>
> AbstractMailRepository.store():165
> ---
> if (!wasLocked) {
> // If it wasn't locked, we need to unlock
> unlock(key);
> synchronized (this) {
> notify();
> }
> }
> -----
>
> If you want to understand why it happens on the first attempt you'll
> have to track all of the "lock()" and "wasLocked" use, but I don't
> understand why you should care of all this low-level stuff for your
> refactoring.
>
> Stefano
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: [EMAIL PROTECTED]
> For additional commands, e-mail: [EMAIL PROTECTED]
>
>
>
--
View this message in context:
http://www.nabble.com/RemoteDelivery-mailet-questions-tp19088399p19092001.html
Sent from the James - Users mailing list archive at Nabble.com.
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
