Navigation issue using jsf, tiles, tomahawk :loosing faces context

Question

Hi all,
I enhanced my webapp using tomahawks jscookmenu.
Triggering 1 menuItem the wanted pages displays correctly but the next click anywhere in the application shows this error:
org.apache.jasper.JasperException: javax.faces.FacesException: Faces context not found. getResponseWriter will fail. Check if the FacesServlet has been initialized at all in your web.xml configuration fileand if you are accessing your jsf-pages through the correct mapping. E.g.: if your FacesServlet is mapped to  *.jsf (with the <servlet-mapping>-element), you need to access your pages as 'sample.jsf'. If you tried to access 'sample.jsp', you'd get this error-message.The web config is like that:
<?xml version="1.0"?>
<web-app xmlns="http://java.sun.com/xml/ns/j2ee"
     xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
     xsi:schemaLocation="http://java.sun.com/xml/ns/j2ee http://java.sun.com/xml/ns/j2ee/web-app_2_4.xsd"
     version="2.4">
     <context-param>
          <description>Tiles MyFaces Config</description>
          <param-name>tiles-definitions</param-name>
          <param-value>/WEB-INF/tiles.xml</param-value>
     </context-param>
     <context-param> 
          <param-name>javax.faces.DEFAULT_SUFFIX</param-name> 
          <param-value>.jsp</param-value>
     </context-param>
     <context-param>
          <param-name>javax.faces.STATE_SAVING_METHOD</param-name>
          <param-value>server</param-value>
     </context-param>
     <context-param>
          <param-name>javax.faces.PARTIAL_STATE_SAVING_METHOD</param-name>
          <param-value>off</param-value>
     </context-param>
     <!-- context-params mafaces -->
     <context-param>
          <param-name>org.apache.myfaces.READONLY_AS_DISABLED_FOR_SELECTS</param-name>
          <param-value>true</param-value>
     </context-param>
     <context-param>
          <param-name>org.apache.myfaces.RENDER_VIEWSTATE_ID</param-name>
          <param-value>true</param-value>
     </context-param>
     <context-param>
          <param-name>org.apache.myfaces.STRICT_XHTML_LINKS</param-name>
          <param-value>true</param-value>
     </context-param>
     <context-param>
          <param-name>org.apache.myfaces.CONFIG_REFRESH_PERIOD</param-name>
          <param-value>this is a bug in myfaces</param-value>
     </context-param>
     <context-param>
          <param-name>org.apache.myfaces.ADD_RESOURCE_CLASS</param-name>
          <param-value>org.apache.myfaces.renderkit.html.util.DefaultAddResource</param-value>
     </context-param>
     <context-param>
          <param-name>org.apache.myfaces.RESOURCE_VIRTUAL_PATH</param-name>
          <param-value>/faces/myFacesExtensionResource</param-value>
     </context-param>
     <context-param>
          <param-name>org.apache.myfaces.CHECK_EXTENSIONS_FILTER</param-name>
          <param-value>true</param-value>
     </context-param>
     <context-param>
          <param-name>org.apache.myfaces.ALLOW_JAVASCRIPT</param-name>
          <param-value>true</param-value>
     </context-param>
     <context-param>
          <param-name>org.apache.myfaces.PRETTY_HTML</param-name>
          <param-value>true</param-value>
     </context-param>
     <context-param>
          <param-name>org.apache.myfaces.AUTO_SCROLL</param-name>
          <param-value>true</param-value>
     </context-param>
     <context-param>
          <param-name>org.apache.myfaces.DETECT_JAVASCRIPT</param-name>
          <param-value>false</param-value>
     </context-param>
     <!-- StartupServletContextListener -->
     <listener>
          <listener-class>
               org.apache.myfaces.webapp.StartupServletContextListener
          </listener-class>
     </listener>
     <!-- Faces MyFacesExtensionsFilter -->
     <filter>
          <filter-name>MyFacesExtensionsFilter</filter-name>
          <filter-class>
               org.apache.myfaces.webapp.filter.ExtensionsFilter
          </filter-class>
          <init-param>
               <param-name>uploadMaxFileSize</param-name>
               <param-value>1m</param-value>
          </init-param>
     </filter>
     <filter-mapping>
          <filter-name>MyFacesExtensionsFilter</filter-name>
          <url-pattern>/faces/*</url-pattern>
     </filter-mapping>
     <filter-mapping>
          <filter-name>MyFacesExtensionsFilter</filter-name>
          <url-pattern>*.jsf</url-pattern>
     </filter-mapping>
     <!-- Faces Servlet -->
     <servlet>
          <servlet-name>Faces Servlet</servlet-name>
          <servlet-class>javax.faces.webapp.FacesServlet</servlet-class>
          <load-on-startup>1</load-on-startup>
     </servlet>
     <!-- Faces Servlet Mapping -->
     <servlet-mapping>
          <servlet-name>Faces Servlet</servlet-name>
          <url-pattern>*.jsf</url-pattern>
     </servlet-mapping>
     <welcome-file-list>
          <welcome-file>index.jsp</welcome-file>
     </welcome-file-list>
     <servlet>
          <servlet-name>imageServlet</servlet-name>
          <servlet-class>my.com.xplorer.gui.v.ImageServlet</servlet-class>
     </servlet>
     <servlet-mapping>
          <servlet-name>imageServlet</servlet-name>
          <url-pattern>/image/*</url-pattern>
     </servlet-mapping>
</web-app>So I lost the faces context using the jscookmenu, I believe.
My webapp uses tiles, and there is 2 navigation possibilities: tomahawaks jscookmenu and tomahawaks commandNavigation.
Latter one runs ok, I do use
<t:panelNavigation id="nav" styleClass="navigation"
     itemClass="navitem" separatorClass="navseparator" 
     activeItemClass="navitem_active" openItemClass="navitem_open">
     <t:commandNavigation action="#{newsHandler.userRequest}" value="#{newsHandler.rss_source_name[0]}">
          <f:param name="navigator"  value="/jsf/news.jsp" />
     </t:commandNavigation>
</t:panelNavigation>for this kind of navigation I do not use any navigation rules in faces config. To dynamically include the desired faces page I do that:
<%
     String s = (String)request.getParameter("navigator");
     if (s == null || s.length() == 0 ) {
          s =  "/jsf/explorer.jsp";
%>
<jsp:include page="<%=s %>" />That does work.
Now like I said I did enhance the app by adding tomahawks jscookmenu.
Therefore I use the following in another tile:
<t:jscookMenu layout="hbr" theme="ThemeOffice" styleLocation="resources/css">
          <%/* Availaible jscookMenu themes: ThemeIE, ThemeMiniBlack, ThemeOffice, ThemePanel
             Availaible jscookMenu layout: hbr, hbl, hur, hul, vbr, vbl, vur, vul
             respect to Heng Yuan http://www.cs.ucla.edu/~heng/JSCookMenu
        */%>
  <t:navigationMenuItem id="nav_0" itemLabel="#{localz.Xplorer}" action="Xplorer" />
</t:jscookMenu>For this kind of navigation I tried to use navigation rules and the following show the config:
     <navigation-rule>
       <from-view-id>/jsf/*</from-view-id>
        <navigation-case>
            <from-outcome>Xplorer</from-outcome>
            <to-view-id>/jsf/tileMain.jsp?navigator=/jsf/explorer.jsp</to-view-id>
        </navigation-case>
        <navigation-case>
            <from-outcome>Tabs</from-outcome>
            <to-view-id>/jsf/tileMain.jsp?navigator=/jsf/tab.jsp</to-view-id>
        </navigation-case>
     </navigation-rule>That works for the first click. The desired page is shown. The nect click anywhere in the app then show the mentioned error.
Using tiles I use this view-handler
<view-handler>org.apache.myfaces.tomahawk.application.jsp.JspTilesViewHandlerImpl</view-handler>One question is: can I use another view-handler on top of the above one? So I could extend com.sun.facelets.FaceletViewHandler and try my luck with this? Or is the solution pointed out just a millisecond from being ok, I just don�t see it?
Maybe you need to know a bit more on how I use tiles:
That is the page I start with. It inserts the tile shown underneath.
<f:view locale="#{userLocale}">
     <f:loadBundle var="localz" basename="my.com.xplorer.gui.v.Lokalization" />
     <f:loadBundle var="bundle" basename="my.com.xplorer.gui.v.messages" />
     <f:subview id="tileMain">
          <h:form id="myJsfForm" styleClass="standard">
                    <tiles:insert definition="template" flush="false" />
          </h:form>
     </f:subview>
     <h:messages />
</f:view>
</html>The foolowing is the tile structure.
The bodi tile is the dynamic part. Above you see that I dynamically load the pages into it.
<t:htmlTag value="div" styleClass="pageLayout">
     <h:panelGrid columns="2" align="center" styleClass="pageContent">
          <f:facet name="header">
               <f:subview id="header">
                    <tiles:insert attribute="header" flush="false" />
               </f:subview>
          </f:facet>
          <t:htmlTag value="div" styleClass="pageMenu">
               <f:subview id="menu">
                    <tiles:insert attribute="menu" flush="false" />
               </f:subview>
          </t:htmlTag>
          <t:htmlTag value="div" styleClass="pageContentWoMenu">
               <f:subview id="bodi">
                    <tiles:insert attribute="bodi" flush="false" />
               </f:subview>
          </t:htmlTag>
          <f:facet name="footer">
               <f:subview id="footer">
                    <tiles:insert attribute="footer" flush="false" />
               </f:subview>
          </f:facet>
     </h:panelGrid>
</t:htmlTag>Maybe you also need to know the tiles config?
<tiles-definitions>
   <definition name="template" path="/jsf/tileTemplate.jsp">
          <put name="header"  value="/jsf/header.jsp"/>
      <put name="menu"    value="/jsf/menu.jsp"/>
      <put name="bodi"    value="/jsf/bodi.jsp"/>
      <put name="footer"    value="/jsf/footer.jsp"/>
   </definition>
   <definition name="/jsf/news.tiles" extends="template">
          <put name="bodi"  value="/jsf/news.jsp"/>
   </definition>
   <definition name="/jsf/explorer.tiles" extends="template">
          <put name="bodi"  value="/jsf/explorer.jsp"/>
   </definition>
   <definition name="/jsf/tab.tiles" extends="template">
          <put name="bodi"  value="/jsf/tab.jsp"/>
   </definition>If you have read until here: thanks very much.
There seems to be a sort of gap regarding jsf navigation documentation.
I mean the ordinary way is covered everywhere (the book I have covers that too), but jscookmenu seems not to fit in too good. I also tried it with an actionslistener in the jscookmenu but that failed, too. So a link to documents telling the truth on jsf navigation I would appreciate very much.
Kind regards
Belle Ile En Mer

Answer 1

This is the error i am getting into now..
exception
org.apache.jasper.JasperException: An exception occurred processing JSP page /welcomeJSF.jsp at line 19
16: This file is an entry point for JavaServer Faces application.
17: --%>
18: <body>
19: <f:view>
20: <h3><h:outputText value="CHOULTRY'S IN BANGALORE" /></h3>
21: <h:form>
22: <table border="0">
Stacktrace:
     org.apache.jasper.servlet.JspServletWrapper.handleJspException(JspServletWrapper.java:505)
     org.apache.jasper.servlet.JspServletWrapper.service(JspServletWrapper.java:416)
     org.apache.jasper.servlet.JspServlet.serviceJspFile(JspServlet.java:342)
     org.apache.jasper.servlet.JspServlet.service(JspServlet.java:267)
     javax.servlet.http.HttpServlet.service(HttpServlet.java:717)
root cause
java.lang.RuntimeException: Cannot find FacesContext
     javax.faces.webapp.UIComponentClassicTagBase.getFacesContext(UIComponentClassicTagBase.java:1811)
     javax.faces.webapp.UIComponentClassicTagBase.setJspId(UIComponentClassicTagBase.java:1628)
     org.apache.jsp.welcomeJSF_jsp._jspx_meth_f_005fview_005f0(welcomeJSF_jsp.java:112)
     org.apache.jsp.welcomeJSF_jsp._jspService(welcomeJSF_jsp.java:86)
     org.apache.jasper.runtime.HttpJspBase.service(HttpJspBase.java:70)
     javax.servlet.http.HttpServlet.service(HttpServlet.java:717)
     org.apache.jasper.servlet.JspServletWrapper.service(JspServletWrapper.java:374)
     org.apache.jasper.servlet.JspServlet.serviceJspFile(JspServlet.java:342)
     org.apache.jasper.servlet.JspServlet.service(JspServlet.java:267)
     javax.servlet.http.HttpServlet.service(HttpServlet.java:717)