According to the a4j loadBundle docs the difference between a4j:loadBundle and f:loadBundle is that the a4j one will mean the resources are there for a4j requests. But I am seeing some behaviour where they are not there. If I have a page a bit like thisThen what I see is that when the region is refreshed, it has no access to the resource bundle; which surprised me (my "required" messages came back as default, rather than what I expected).
If I move the loadBundle declaration to within the region, it works OK; but obviously I then lose the ability to refer to it earlier on in the page.
In the linked document, it states that in JSF 1.2 it is possible to declare a bundle in faces-config.xml and that this overcomes the limitation with f:loadBundle, so I tried that and didn't see any change; resource no available when region refreshed.
In this case I just did away with the region (luckily chnages to the page allowed me to do that). But I am still a bit puzzled as to what is going on as I was careful to make sure it was within f:view and that is all the documentation seemed to indicate would be required.