6 Jan
2009
6 Jan
'09
5:29 p.m.
On Jan 6, 2009, at 5:17 PM, Fabio Mancinelli wrote:
Thanks
-Vincent
http://xwiki.com
http://massol.net
http://xwiki.org
Vincent Massol wrote:
ok be very very careful with this. We've been beaten already in the
past by this and it took me several days to find out the problem...
Are we storing any state in the resource components?
Hi Fabio,
I can't see the reply you got on the list.
The Tigris platform is not good at all.
Anyway it's here:
http://restlet.tigris.org/ds/getDSMessageAttachment.do/attachment-1305329?d…
Also I think you've introduced an important
bug: whenever plexus
instantiates a per-lookup component a new instance is created but you
have to release it explicitely as otherwise it won't be released.
Which means you'll get an out of memory exception very quickly.
per-look must be avoided as much as possible (we don't have any in
the
other components of xwiki because of the release problem).
Ok I see. Well, here we don't have the choice so I am going to try to
put in place some mechanism to release resource objects. Also I
don't understand why something like XmlTextSpacesRepresenter
should not be a singleton.
They can be singletons provided that they are thread-safe.
Taking into account what you said before, I am going to declare them
as
singletons.
-Fabio