You are viewing a plain text version of this content. The canonical link for it is here.
Posted to users@myfaces.apache.org by Ro...@equifax.com on 2008/08/27 15:50:09 UTC

Trinidad skin selection failing on initial visit for each session

This is a resend of a message from Christian Hall.  His email was rejected 
due to too high of a spam score.  I am retrying.

We are using a skin whose family property in the config file is set to 
resolve via an expression using a session scoped bean (e.g. 
#{sessionScope.userContext.skinFamily}).

Upon the first visit to the page, the default minimal skin is used and on 
the second visit it uses our skin. As best I can tell from debugging, it 
just doesn't run our code during the stylesheet component's encoding 
(we're actually using trh:head) but waits until the body tag writes a 
debug comment to the page. The comment says something to the effect of 
"skin: minimal (custom)" where custom is our custom skin family...so at 
that point, it runs our code, sees our custom family and the next page 
works...but that first rendering for each session gets the minimal skin.

Is this a known issue? Anyone seen this?

Thanks,

Robert Bowen
Enterprise Planning and Architecture
770-740-6869 (office)
770-310-9556 (mobile)

Re: Trinidad skin selection failing on initial visit for each session

Posted by Christian Hall <ch...@alltel.net>.
This is a repost due to email difficulties at work I posted the answer a few
days back. Drop the sessionScope and it works.


----- Original Message ----- 
From: "Matthias Wessendorf" <ma...@apache.org>
To: "MyFaces Discussion" <us...@myfaces.apache.org>
Sent: Monday, September 01, 2008 8:45 AM
Subject: Re: Trinidad skin selection failing on initial visit for each
session


> why using sessionScope.blah at all ?
> I'd suggest to use only blah.foo, when your bean is correctly configured
>
> On Mon, Sep 1, 2008 at 1:28 PM, Frank Nimphius
> <fr...@oracle.com> wrote:
> > Robert,
> >
> > could this have to do with when you set your skin to the session
attribute.
> > If you try
> >
> >
#{sessionScope.userContext.skinFamily"=null?sessionScope.userContext.skinFam
ily:'custom'}
> >
> > would that solve the issue?
> >
> > Frank
> >
> >
> > Robert.Bowen@equifax.com wrote:
> >
> > This is a resend of a message from Christian Hall.  His email was
rejected
> > due to too high of a spam score.  I am retrying.
> >
> > We are using a skin whose family property in the config file is set to
> > resolve via an expression using a session scoped bean (e.g.
> > #{sessionScope.userContext.skinFamily}).
> >
> > Upon the first visit to the page, the default minimal skin is used and
on
> > the second visit it uses our skin. As best I can tell from debugging, it
> > just doesn't run our code during the stylesheet component's encoding
(we're
> > actually using trh:head) but waits until the body tag writes a debug
comment
> > to the page. The comment says something to the effect of "skin: minimal
> > (custom)" where custom is our custom skin family...so at that point, it
runs
> > our code, sees our custom family and the next page works...but that
first
> > rendering for each session gets the minimal skin.
> >
> > Is this a known issue? Anyone seen this?
> >
> > Thanks,
> >
> > Robert Bowen
> > Enterprise Planning and Architecture
> > 770-740-6869 (office)
> > 770-310-9556 (mobile)
> >
> > --
> >
> > Frank Nimphius | Principal Product Manager
> > Oracle Application Development Tools
> > Oracle is committed to developing practices and products that help
protect
> > the environment
>
>
>
> -- 
> Matthias Wessendorf
>
> Need JSF and Web 2.0?
> http://code.google.com/p/facesgoodies
>
> further stuff:
> blog: http://matthiaswessendorf.wordpress.com/
> sessions: http://www.slideshare.net/mwessendorf
> mail: matzew-at-apache-dot-org


Re: Trinidad skin selection failing on initial visit for each session

Posted by Matthias Wessendorf <ma...@apache.org>.
why using sessionScope.blah at all ?
I'd suggest to use only blah.foo, when your bean is correctly configured

On Mon, Sep 1, 2008 at 1:28 PM, Frank Nimphius
<fr...@oracle.com> wrote:
> Robert,
>
> could this have to do with when you set your skin to the session attribute.
> If you try
>
> #{sessionScope.userContext.skinFamily"=null?sessionScope.userContext.skinFamily:'custom'}
>
> would that solve the issue?
>
> Frank
>
>
> Robert.Bowen@equifax.com wrote:
>
> This is a resend of a message from Christian Hall.  His email was rejected
> due to too high of a spam score.  I am retrying.
>
> We are using a skin whose family property in the config file is set to
> resolve via an expression using a session scoped bean (e.g.
> #{sessionScope.userContext.skinFamily}).
>
> Upon the first visit to the page, the default minimal skin is used and on
> the second visit it uses our skin. As best I can tell from debugging, it
> just doesn't run our code during the stylesheet component's encoding (we're
> actually using trh:head) but waits until the body tag writes a debug comment
> to the page. The comment says something to the effect of "skin: minimal
> (custom)" where custom is our custom skin family...so at that point, it runs
> our code, sees our custom family and the next page works...but that first
> rendering for each session gets the minimal skin.
>
> Is this a known issue? Anyone seen this?
>
> Thanks,
>
> Robert Bowen
> Enterprise Planning and Architecture
> 770-740-6869 (office)
> 770-310-9556 (mobile)
>
> --
>
> Frank Nimphius | Principal Product Manager
> Oracle Application Development Tools
> Oracle is committed to developing practices and products that help protect
> the environment



-- 
Matthias Wessendorf

Need JSF and Web 2.0?
http://code.google.com/p/facesgoodies

further stuff:
blog: http://matthiaswessendorf.wordpress.com/
sessions: http://www.slideshare.net/mwessendorf
mail: matzew-at-apache-dot-org