You were rgh Martin.
I switched back to 1.1.1 and it worked spotlessly.
An error can be in a tiny corner sometimes.
Thx for help,
Philippe
On 21 Feb 2006, at 07:42, Martin Marinschek wrote:
I see a method in your stack-trace that has been abandoned after some
time - maybe you use a nightly where this is still in, and this is
causing the difference.
Namely: ExtensionFilter.getFacesContext()
regards,
Martin
On 2/20/06, Philippe Lamote <[EMAIL PROTECTED]> wrote:
Thx.
My bean has "session" scope too.
The only diff I see is my page code is not inside a "facet", yet I
don't think this (should) make any difference.
I'm out of ideas.
Philippe
On 20 Feb 2006, at 22:29, Carsten Burghardt wrote:
Am Monday 20 February 2006 22:18 schrieb Philippe Lamote:
Too bad :-(
Setting "immediate" to "true" is certainly an enhancement, (speed-
wise) yet it doesn't change anything here.
Have you changed other things as well perhaps?
Philippe
Nope but lets try the complete thingy:
<f:facet name="logout">
<h:panelGroup>
<t:graphicImage value="images/small/exit.png" border="0"/>
<f:verbatim> </f:verbatim>
<h:commandLink immediate="true" action="#
{navigationBean.logoutAction}"
styleClass="root">
<h:outputText value="#{node.description}"/>
</h:commandLink>
</h:panelGroup>
</f:facet>
public String logoutAction()
{
rootNode = null;
try {
// remove the user from the session
serviceLocator.getUserService().logout();
} catch (ServiceException e) {
// ignore
}
// invalidate the session
HttpSession session = (HttpSession)
FacesContext.getCurrentInstance().getExternalContext().getSession
(false);
session.invalidate();
return INavigationResults.LOGIN;
}
The backing bean is session based.
Carsten
--
http://www.irian.at
Your JSF powerhouse -
JSF Consulting, Development and
Courses in English and German
Professional Support for Apache MyFaces
