You are viewing a plain text version of this content. The canonical link for it is here.
Posted to users@myfaces.apache.org by Francisco Passos <fr...@gmail.com> on 2007/08/24 11:12:50 UTC
Myfaces 1.1.5 and JSTL 1.1.0
Good day!
I know JSTL is more fully supported in the JSF 1.2 branch of Myfaces.
However, I'd like to know specifically what does not or might not work
properly when using the JSTL library on myfaces 1.1.5.
Thank you,
Francisco Passos
Re: Re: [Facelets] Template problems
Posted by Rain <bi...@gmail.com>.
Andrew Robinson:
你好!
That works!
Thanks.
Rain.
2007-08-27
发件人： Andrew Robinson
发送时间： 2007-08-27 12:06:33
收件人： MyFaces Discussion; bingyu1108@gmail.com
抄送：
主题： Re: [Facelets] Template problems
put <ui:composition > in every included file to trim out the content
you don't want included.
On 8/26/07, Rain <bingyu1108@gmail.com > wrote:
>
>
> Hi ,Everyone:
>
> When i use Faceltes template, I have to add
> <?xml version="1.0" encoding="gbk"? >
> in every pages header. and this cause a problem is that the client browser
> page will have a lot of
> <?xml version="1.0" encoding="gbk"? >. this is not work in firefox.
>
> so how configure the facelets can fix this problem.
>
> Any help.Thanks.
>
> Rain.
>
>
>
> 2007-08-27
> ________________________________
>
Re: [Facelets] Template problems
Posted by Andrew Robinson <an...@gmail.com>.
put <ui:composition> in every included file to trim out the content
you don't want included.
On 8/26/07, Rain <bi...@gmail.com> wrote:
>
>
> Hi ,Everyone:
>
> When i use Faceltes template, I have to add
> <?xml version="1.0" encoding="gbk"?>
> in every pages header. and this cause a problem is that the client browser
> page will have a lot of
> <?xml version="1.0" encoding="gbk"?>. this is not work in firefox.
>
> so how configure the facelets can fix this problem.
>
> Any help.Thanks.
>
> Rain.
>
>
>
> 2007-08-27
> ________________________________
>
[Facelets] Template problems
Posted by Rain <bi...@gmail.com>.
Hi ,Everyone:
When i use Faceltes template, I have to add
<?xml version="1.0" encoding="gbk"?>
in every pages header. and this cause a problem is that the client browser page will have a lot of
<?xml version="1.0" encoding="gbk"?>. this is not work in firefox.
so how configure the facelets can fix this problem.
Any help.Thanks.
Rain.
2007-08-27
Re: Myfaces 1.1.5 and JSTL 1.1.0
Posted by Francisco Passos <fr...@gmail.com>.
Thank you for clearing this up for me.
Is it part of the plan to make these situations work? Or are they structural
limitations with no workaround?
On 8/25/07, simon <si...@chello.at> wrote:
>
> On Fri, 2007-08-24 at 10:12 +0100, Francisco Passos wrote:
> > Good day!
> >
> > I know JSTL is more fully supported in the JSF 1.2 branch of Myfaces.
> > However, I'd like to know specifically what does not or might not work
> > properly when using the JSTL library on myfaces 1.1.5.
>
> JSTL expressions that can change the number of JSF components in the
> view are the main issue So things like having a JSF component within a
> c:if or a c:forEach is a problem.
>
> I think c:if/c:forEach are ok if the condition of the if/forEach does
> not change during the lifetime of the view. I've certainly used c:if
> successfully with JSF to conditionally include subviews, but the subview
> never "disappeared" while the view was active...
>
> Regards,
>
> Simon
>
>
>
Re: Myfaces 1.1.5 and JSTL 1.1.0
Posted by simon <si...@chello.at>.
On Fri, 2007-08-24 at 10:12 +0100, Francisco Passos wrote:
> Good day!
>
> I know JSTL is more fully supported in the JSF 1.2 branch of Myfaces.
> However, I'd like to know specifically what does not or might not work
> properly when using the JSTL library on myfaces 1.1.5.
JSTL expressions that can change the number of JSF components in the
view are the main issue So things like having a JSF component within a
c:if or a c:forEach is a problem.
I think c:if/c:forEach are ok if the condition of the if/forEach does
not change during the lifetime of the view. I've certainly used c:if
successfully with JSF to conditionally include subviews, but the subview
never "disappeared" while the view was active...
Regards,
Simon