This looks good for the memory leak but... if we're going to change the API, why not just store the cache in the JellyContext and be done with it?
I would have nothing against it... I think there's no way to avoid changing the API as things are really pulled from everywhere.
Is there a patch for the jelly-context already ?
(and do I understand correctly that, anyways, the modification would only be enrichment of the API ?).
paul
--------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
