the reason in plexus was because each action was allocated on every
request and not released - I just want to check whether that was the
case again here. I think Olivier investigated it originally - is he
listening here? :)
- Brett
On 29/02/2008, at 7:43 PM, nicolas de loof wrote:
// Release existing
- release( archivaConfiguration );
+// FIXME spring equivalent ? release( archivaConfiguration );
I don't know if spring takes care of managing them itself - but we
need to look into this since we used to have leaks from the webapp
when it never released the components.
AFAIK there is no way in spring to "remove" a bean from the context.
Not sure what is the requirement here, I suppose we want to FORCE the
singleton "archivaConfiguration" bean to get reloaded / refreshed.
The best option IMHO is to use use a BeanNameAutoProxyCreator to
create a
proxy for the "archivaConfiguration" singleton. An interceptor could
cache
the active concrete implementation instance, declared as prototype,
and
expose a "release()" management method to force a new lookup.
Nicolas.
--
Brett Porter
[EMAIL PROTECTED]
http://blogs.exist.com/bporter/
