Yes, that issue just confirms that the interaction between ui:include/ui:decorate/ui:composition is very confusing :-) I remember reading through it before when the discussion was active.
I am replacing "ui:include src=" with "ui:decorate template=" -- it seems like a strange way to do it, but no error so far, and I can move on to my next JSF2.0/richfaces4 conversion issue :-) Thanks. On Thu, Dec 15, 2011 at 11:49 AM, Leonardo Uribe <[email protected]> wrote: > Hi > > When you use ui:include, inside myfaces a new template context is created, > and all template logic including template params are "isolated", which > means > params passed or earlier ui:define or ui:insert declarations will be > ignored. > > So it is expected ui:param definitions does not pass through ui:include, > unless > you define a ui:param inside ui:include and declare in a explicit way that > this param will be used inside that template. Other option is use > ui:decorate instead ui:include, so the same template context will be used > to resolve your template. > > The issue related to this behavior is: > > https://issues.apache.org/jira/browse/MYFACES-2753 > Trivial multi-level templating does not work if ui:include is used > > regards, > > Leonardo Uribe >
