-
Feature Request
-
Resolution: Done
-
Major
-
None
-
None
-
None
Max tells my that, today, when a resource bundle is defined using f:loadBundle, we can actually look inside the .properties file and find the keys.
Well, thats awesome, except that f:loadBundle is semi-deprecated, and the following approaches are preferred:
- For Seam projects, use the built-in component, and do #
{messages.foo}
to get "foo" from messages_xx.properties
- For any JSF project, look at resource bundles defined in faces-config.xml
By the way, at present it looks like the resource bundle stuff is a bit confused about the classpath, and thinks that if the bundle.properties file is in src/model, then the name of it is "model.bundle", when in fact it is just "bundle". This is a bug.
- is duplicated by
-
JBIDE-1136 Code assist for seam messages component
- Closed
- is related to
-
JBIDE-1271 Visual Editor should use resource bundles for preview
- Closed
-
JBIDE-2011 Resources with dot's are handled wrong in code completion
- Closed
- relates to
-
JBIDE-1259 Resource bundle in faces-config.xml has hard coded src path
- Closed