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
[EMAIL PROTECTED] 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 |
|
