: Behavior change for ui:params
Hi
Yes, I know, but note the current behavior is the most desirable
because it prevents
a lot of side effects (including the ones described on MYFACES-2753 and
others)
and is the closest one with the spec.
regards,
Leonardo Uribe
Under JSF 1.2 and Facelets, you could specify a ui:param value as a child
of ui:decorate, and it would be used in any included files.
Under JSF 2.1, the ui:param value evaluates to null in the included files
unless it is passed as a child of the ui:include.
Is this a bug or a spec-required change
Hi
The javadoc of ui:param says this:
...Use this tag to pass parameters to an included file (using
ui:include), or a template (linked to either a composition or
decorator). Embed ui:param tags in either ui:include, ui:composition,
or ui:decorate to pass the parameters. ...
In myfaces this was
Outside of ui:define body is actually the original state of the JSF 1.2
template -- I had moved it around while trying to debug the problem, and
forgot to move it back when writing up this email.
Are you saying that if I have ui:param outside of ui:define body, it
should work for files included
Outside of ui:define body is actually the original state of the JSF 1.2
template -- I had moved it around while trying to debug the problem, and
forgot to move it back when writing up this email.
Are you saying that if I have ui:param outside of ui:define body, it
should work for files included
Hi
Yes, because ui:param defines a param for the template.
regards,
Leonardo Uribe
Well, it's not working :-) I've spent a couple of days now trying to
track this one down.
As I said before, the best I can determine is that the value of
sourcePage evaluates to null while in the included fragment in body -- I
am thinking that the scope of ui:param is the cause of the problem.
Spam Assassin keeps bouncing my emails...
===
Well, it's not working :-) I've spent a couple of days now trying to
track this one down.
As I said before, the best I can determine is that the value of
sourcePage evaluates to null while in the included fragment in body -- I
am thinking
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
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
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
Hi
Yes, I know, but note the current behavior is the most desirable
because it prevents
a lot of side effects (including the ones described on MYFACES-2753 and others)
and is the closest one with the spec.
regards,
Leonardo Uribe
12 matches
Mail list logo
