Hi Pierre,
The main thing that bothers me is that it imposes a bunch of
standard property names for something as basic and generic as
ElementSupport. It doesn't feel right to me.
OK, I put them with all the specific methods in a
ElementTranslatorSupport class.
That's already a good step, but if you think about it. This is really
related to a specific TranslatorSupport implementation that allows
configuration through element properties. I this think it should be
put in a concrete implementation or in an abstract base class if you
have several relying on this.
Actually, no. You can already use it now and provide the
TranslatorSupport instance from a participant. Full IoC reference
factory support isn't required for you to implement it. It's
might just be handy to have for people that declare their site
structures in XML and want to also declare an IoC reference in
there. Using Java, Groovy and Janino for the site structure
doesn't required this support at all.
OK. The above class is a first step in this direction. It's now
possible to use it by default, and if needed to specify a other
TranslatorSupport for each element. I'll commit this as soon I have
finish to complete the comments.
Possibly next step: start with the participant stuff but as i see
the thing, it'll be to intanciate directly a Translator.
What do you mean with this second step? Can you explain it in more
detail?
I understood that, I'm more looking for a real-world use case
that warrants this feature. I can see why it might be
theoretically interesting, but doubt that it warrants the API
complexity increase in practice.
I propose a compromise: I remove "withDefault" and keep a
"withTopPriority"
Lol, I'm not looking for a compromise but for a detailed real world
example of why this is needed, and why it needs to be there in the
API. If you can convince me it's important, they can both just stay ;-)
Best regards,
Geert
--
Geert Bevin Uwyn bvba GTalk: [EMAIL PROTECTED]
"Use what you need" Avenue de Scailmont 34 Skype: gbevin
http://www.uwyn.com 7170 Manage, Belgium AIM: geertbevin
gbevin at uwyn dot com Tel: +32 64 84 80 03 Mobile: +32 477 302 599
PGP Fingerprint : 4E21 6399 CD9E A384 6619 719A C8F4 D40D 309F D6A9
Public PGP key : available at servers pgp.mit.edu, wwwkeys.pgp.net
_______________________________________________
Rife-users mailing list
[email protected]
http://lists.uwyn.com/mailman/listinfo/rife-users