Yep, I'll look into this. Probably will come back with some questions later
:-)
Gunnar
2010/2/18 Emmanuel Bernard
> OK so let's prototype that then:
> - implement a service locator style way of declaring / finding resource
> bundles (not resource bundle files)
> - implement a ResourceBundle
OK so let's prototype that then:
- implement a service locator style way of declaring / finding resource
bundles (not resource bundle files)
- implement a ResourceBundle aggregator that gives priority to
ValidationMessages
- see how bad/good that can play with
http://opensource.atlassian.com/
On Tue, 16 Feb 2010 18:41:12 -0300, Gunnar Morling
wrote:
> I agree with Max, I think there should be some way for packaging message
> bundles within components containing constraint annotations, while
> offering
> the possibility to optionally override these with custom messages if
> require
I agree with Max, I think there should be some way for packaging message
bundles within components containing constraint annotations, while offering
the possibility to optionally override these with custom messages if
required.
With respect to large-scale enterprise apps, I guess it can become qui
On 16 févr. 2010, at 09:58, Max Rydahl Andersen wrote:
>
> - "Emmanuel Bernard" wrote:
>
>> I don't see i18n as something that should necessarily be packaged
>> inside a component. Resource keys are generally grouped in one or two
>> files for the overall application (so that fixing a typo
- "Emmanuel Bernard" wrote:
> I don't see i18n as something that should necessarily be packaged
> inside a component. Resource keys are generally grouped in one or two
> files for the overall application (so that fixing a typo is quick).
You must be developing small or monolith applications
I don't see i18n as something that should necessarily be packaged inside a
component. Resource keys are generally grouped in one or two files for the
overall application (so that fixing a typo is quick). If you have to dig into
individual or even third party components, it becomes a pain point.
Hi,
Having multiple resource bundles and some custom way of specifying these
bundles is
related to HV-238 and HV-251.
Having a ResourceBundleLocatorStrategy should solve your problem Gunnar,
right?
The default strategy could behave like it does now and we can provide an
additional strategy
