[seam-issues] [JBoss JIRA] Updated: (SEAMINTL-25) AvailableLocales.locales always has zero elements when configuration follows the documentation
[
https://issues.jboss.org/browse/SEAMINTL-25?page=com.atlassian.jira.plugi...
]
Sebastian Sachtleben updated SEAMINTL-25:
-----------------------------------------
Status: Pull Request Sent (was: Open)
Git Pull Request: https://github.com/seam/international/pull/5
Several problems solved. First the configuration wasnt properly parsed. The Config module
took the Instance and not as List directly. It wasnt possible to set up more than one
locale. Currently I'm not sure if one worked before. I have added a new configuration
class with a set of locale which parsed perfectly from seam-beans.xml now.
In AvailableLocals.java the init method failed allways on
!supportedLocaleKeys.isUnsatisfied() before. Now with the configuration the problem is
solved and the list of locales will be proved correctly.
I have also changed the test and docbook to complete this bugfix.
AvailableLocales.locales always has zero elements when configuration
follows the documentation
----------------------------------------------------------------------------------------------
Key: SEAMINTL-25
URL: https://issues.jboss.org/browse/SEAMINTL-25
Project: Seam International
Issue Type: Bug
Components: Locales
Affects Versions: 3.0.0.Beta2
Environment: JBAS6.0.0.Final
Reporter: Leiv Hellebo
Assignee: Ken Finnigan
Fix For: 3.0.0.CR1
Attachments: NoLocale.java, seamintl-nolocales.war
AvailableLocales has @Produces List<Locale> locales, but the list is always empty
Stepping through the code in debug mode shows that no locales is added because the
if-test of line 55 (!supportedLocaleKeys.isUnsatisfied()) is never true
(and a side note: the log says "WELD-000604 interface
org.jboss.seam.international.locale.SupportedLocaleKeys is not declared @Target(METHOD,
FIELD, PARAMETER, TYPE). Weld will use this annotation, however this may make the
application unportable." otherwise nothing in the logs)
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira