[
https://issues.apache.org/struts/browse/WW-2774?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
James Holmes updated WW-2774:
-----------------------------
Fix Version/s: Future
Issue Type: Improvement (was: Bug)
I would consider this to be an improvement and not a bug.
Can you provide a patch? If so, we can get this integrated much faster.
> default resource bundles don't load via TextProvider (they have to load via
> ResourceBundle.getBundle)
> -----------------------------------------------------------------------------------------------------
>
> Key: WW-2774
> URL: https://issues.apache.org/struts/browse/WW-2774
> Project: Struts 2
> Issue Type: Improvement
> Components: Other
> Affects Versions: 2.0.11.2
> Reporter: Brian Repko
> Fix For: Future
>
>
> LocalizedTextUtil.findDefaultText calls LocalizedTextUtil.findResourceBundle
> directly in order to load ResourceBundles rather than going through
> TextProvider.getTexts. By having defaults come from TextProvider we can
> implement ResourceBundles that come from Spring (MessageSource) or implement
> our own factories (including calling ResourceBundle.getBundle with a
> ResourceBundle.Control object on JDK6).
> We have a database-based content management system that does not implement
> ResourceBundle but does implement MessageSource. We plan to use the Spring
> classes to wrap MessageSource but cannot do so for default messages. Our
> fallback is to name our MessageSources based on packages / classes and have
> nothing in the defaults except for xwork-messages.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
