When you have a page using these composites:
and that these composites use a resource bundle by the mean of <f:loadBundle>
for their own work, you have to take care of using a unique variable for each of
If you attempt to ease your coding by using the same variable each time in all
your composites, such as here (using x):
<html xmlns="http://www.w3.org/1999/xhtml" [...]>
<f:loadBundle basename="myWork_a" var="x" />
Then <myTools:a/>, <myTools:b/>, and <myTools:c/> will use the same bundle,
whatever their own basename is saying. (I don't remember if only the basename of
the myWork_a bundle will be used or only myWork_c).
Then, we have to find unique variables one to ensure our composite won't have
bundle variables that could collide. Like:
<f:loadBundle basename="myWork_a" var="xa" /> for component a,
<f:loadBundle basename="myWork_b" var="xb" /> for component b,
<f:loadBundle basename="myWork_c" var="xc" /> for component c.
and of course, it's a bit boring. The problem comes from <f:loadBundle> that has
a request scope, I think. Can something be done to allow it having only the
strict composite scope (= no scope at all?).