When do you need to register the message bundle in the faces-config

Question

hello
i have applied two examples to localize messages, label, title by creating message.properties file and utilizing the f:loadbundle component the EL expression. It works like a charm without having to register anything, I have only registered the locale, but not the bundle
also , i have used a programmatic approach
FacesContext fc = FacesContext.getCurrentInstance();
ResourceBundle msg = ResourceBundle.getBundle("message",fc.getViewRoot().getLocale());
fc.addMessage(FacesMessage.SEVERITY_FATAL.toString(),new FacesMessage(msg.getString("ok")));
which also worked without registering the message bundle!!
although many article i read ask to register the message bundle.
Another thing is that in Oracle Jdeveloper 10g for FORMS and PL/SQL Developers states that the message file needs to be located in \resource subdirectory
and using getBundle (resources.message) to get it. In fact i kept getting errors indicating that the base bundle cannot be read until i located the file in the ViewContoller directory itself (and that is why i reference it with getBundle("message") rather than resources.message as indicated in the book.
appreciate your response
ammar sajdi
amman - jordan

Answer 1

Hi,
Your question is not very clear. But let get through some various guideline.
<f:loadBundle/> is horribly buggy and was all but removed from the specification. As a tag, it gets only evaluated during the render view phase, meaning that if you have EL expression referring the loadBundle's var during another phase, it's going to fail. The most common case is during validation with overridden messages.
About the programmatic access, the problem is that you're linking your application to a specific bundle at code level. Meaning that you're preventing it to be reused in a different context, while the following get the most application local bundle name (faces-config.xml's message-bundle property)
Resourcebundle.getBundle(FacesContext.getApplication().getMessageBundle())Registration is also the only way to override the default conversion / validation messages.
For JSF 1.1 (10g), those are your option. However, if you're using JSF 1.2 (11g), you can also register resource bundles in the faces-config file, you then register the bundle and the var associated to it, removing the need of f:loadBundle and fixing the non render phase issues. furthermore, the code version is also simplified to:
FacesContext context = FacesContext.getCurrentInstance();
ResourceBundle bundle = context.getApplication().getResourceBundle(context, "varName");
bundle.getString("myKey");You other part about \resource I never heard of nor cared for. You can place the bundle where you like on the classpath.
Regards,
~ Simon