Geert,
Since it should not store the element instance in the
LocaleProvider instance. The instance will be constructor
through IoC and the element instance is not known in that
context. It's also much more appropriate since the element
instance changes at each request, and otherwise you'd have to
create a new LocaleProvider instance for each request.
If we want to avoid creation of LocalProvider instance with each
element instance, the only way I see is to store the LocalProvider
in a global variable. Is it right?
No, if they are injected through IoC, the reference factory can
either provide the LocalProvider as a singleton,
singleton: is there no risk of confusion between 2 or more elements from
different threads?
either instantiate it at each use. This can then be injected into a
property. We still need to add simple reference factory features to
RIFE itself currently it delegates that to a repository participant
can you give me a link to any howto.
where you either do it in plain Java or interface with an IoC
container like Spring or Pico.
Regrards
Pierre
_______________________________________________
Rife-users mailing list
[email protected]
http://www.uwyn.com/mailman/listinfo/rife-users
