There are known issues with JSTL and JSF but I am not an expert enough at either to say for sure this is your problem. I take it you are aware that you are not really supposed to be mixing the two right? The new JSF spec seems to make big strides in that area however.
sean On 4/20/05, Werner Punz <[EMAIL PROTECTED]> wrote: > Hi, I am currently in the migration process > from 1.0.9 myfaces RC1 to the final one. > I have following construct in my navigation: > > <%@ taglib uri="http://java.sun.com/jsf/html"; prefix="h"%> > <%@ taglib uri="http://java.sun.com/jsf/core"; prefix="f"%> > <%@ taglib uri="http://myfaces.apache.org/extensions"; prefix="x"%> > <%@ taglib prefix="c" uri="/WEB-INF/c-rt.tld" %> > <x:panelNavigation id="nav" > styleClass="navigation" > > itemClass="navitem" > activeItemClass="navitem_active" > openItemClass="navitem_open" > > <c:if test="${userData.loggedIn}"> > ... a few links > </c:if> > <c:if test="${!userData.loggedIn}"> > <f:verbatim>whatever text for not logged in</f:verbatim> > </c:if> > </x:panelNavigation> > > the jstl is also specified in the web.xml > > <taglib> > <taglib-uri>http://java.sun.com/jstl/core</taglib-uri> > <taglib-location>/WEB-INF/c-rt.tld</taglib-location> > </taglib> > > <taglib> > <taglib-uri>http://java.sun.com/jstl/core-rt</taglib-uri> > <taglib-location>/WEB-INF/c-rt.tld</taglib-location> > </taglib> > > and the affected object is also in my faces-config.xml > > <managed-bean> > <managed-bean-name>userData</managed-bean-name> > <managed-bean-class>sapjvac.misc.UserData</managed-bean-class> > <managed-bean-scope>session</managed-bean-scope> > </managed-bean> > > The funny thing is, from myfaces, the bean is called properly, > but it is not accessed by the jstl tags directly. It used to work before > 1.0.9 (probably my mistake) > > I must be something missing here. > >
