On Apr 14, 2009, at 16:22, Sanne Grinovero wrote:
I'm going for the Map approach, to favor cleaner code and because you
appear to be more comfortable with it.
Even so there are two more points to consider:
1)If in the future a code change of the Synchronization (stored in the
WeakMap as a val
I'm going for the Map approach, to favor cleaner code and because you
appear to be more comfortable with it.
Even so there are two more points to consider:
1)If in the future a code change of the Synchronization (stored in the
WeakMap as a value)
would be changed in any way to get a (hard) referen
On Apr 14, 2009, at 13:03, Sanne Grinovero wrote:
I've 2 inline answers:
2009/4/14 Emmanuel Bernard :
Read inline
On Apr 13, 2009, at 17:22, Sanne Grinovero wrote:
After our chat about the topic I thought that I only needed some
minor
changes,
was quite wrong.
I moved the flush listen
I've 2 inline answers:
2009/4/14 Emmanuel Bernard :
> Read inline
>
> On Apr 13, 2009, at 17:22, Sanne Grinovero wrote:
>
>> After our chat about the topic I thought that I only needed some minor
>> changes,
>> was quite wrong.
>>
>> I moved the flush listener to the usual FullTextIndexEventListe
Read inline
On Apr 13, 2009, at 17:22, Sanne Grinovero wrote:
After our chat about the topic I thought that I only needed some
minor changes,
was quite wrong.
I moved the flush listener to the usual FullTextIndexEventListener,
using
delegation at first as we had agreed. This got me into
After our chat about the topic I thought that I only needed some minor changes,
was quite wrong.
I moved the flush listener to the usual FullTextIndexEventListener, using
delegation at first as we had agreed. This got me into troubles with
the Serialization test of the FullTextEntityManager, I had
