facesContext should exist as a request variable. At least with Facelets I know this is true from others mentioning it. I'm not sure why it wouldn't be working for you. If you are using facelets, JSP variables will not be available (sessionScope for example).
Here is the list of variables that should be available if you are rendering using JSP according to Sun: http://java.sun.com/j2ee/1.4/docs/tutorial/doc/JSPIntro7.html If you are using facelets, I am not sure which are available (I couldn't find hit for this quickly) (I know that all the JSP variables are not available). JSF should not interfere with JSP variables being available or not via EL unless there is a problem in the EL resolver. On 4/10/06, Werner Punz <[EMAIL PROTECTED]> wrote: > Frank Schaare schrieb: > > Hallo, > > > > i'm trying to display the session information (like creationTime or > > sessionID) within an JSF EL Variable. > > > > I tried #{sessionScope.creationTime} which is ignored from the renderer. > > Likewise #{facesContext.externalContext.session.creationTime} or > > #{facesContext.currentInstance.externalContext.session.creationTime} > > does not work for me. > > > > I's like to avoid mixing JSF and JSP EL together, is there a chance to > > get the needed Info through JSF EL ? > > > you have to set a managed bean with properties which deliver the values > that should do it. > The facesContent, and sessionScope objects are not managed beans to my > knowledge. > >
