hi gunnar,

since it isn't a complicated topic, we can write a proposal as soon as we have a basic agreement about the approach.

imo it's pretty easy - it's just about:

 - an interface which directly allows simple but still flexible custom implementations of (custom) message-sources (including a simple delegation to a ResourceBundle).
vs.
 - an interface which is restricted to ResourceBundle. -> if it isn't possible to use ListResourceBundle or PropertyResourceBundle, users have to implement #getKeys which might not be possible (/ that easy) for some advanced use-cases.

the rest is more or less the same - if the MessageInterpolator receives a key, it uses the new interface for the lookup (if there is no custom implementation of the new interface or no result for the given key, the existing default bundle (ValidationMessages) is used as a fallback).

regards,
gerhard



2012/6/26 Gunnar Morling <gunnar@hibernate.org>

Hi Gerhard,

I thin I've not yet totally understood what you have in mind.
Maybe you could create a proposal for BVAL-217 describing things more in detail (interaction between resolver and interpolator, integration with BV 1.0 interpolators etc.)?
I also think using resource bundles is not totally optional as there is the ValidationMessages bundle.

--Gunnar

Am 25.06.2012 18:49 schrieb "Gerhard Petracek" <gerhard.petracek@gmail.com>:

_______________________________________________
beanvalidation-dev mailing list
beanvalidation-dev@lists.jboss.org
https://lists.jboss.org/mailman/listinfo/beanvalidation-dev