About jsf and tiles

Good days , the following exception is happening:
javax.faces.FacesException
at de.mindmatters.faces.lifecycle.RenderResponsePhase.executePhase(RenderResponsePhase.java:53)
at de.mindmatters.faces.lifecycle.AbstractPhase.execute(AbstractPhase.java:37)
at de.mindmatters.faces.lifecycle.LifecycleImpl.executePhase(LifecycleImpl.java:166)
at de.mindmatters.faces.lifecycle.LifecycleImpl.render(LifecycleImpl.java:226)
at javax.faces.webapp.FacesServlet.service(FacesServlet.java:138)
at org.mortbay.jetty.servlet.ServletHolder.handle(ServletHolder.java:487)
at org.mortbay.jetty.servlet.ServletHandler.handle(ServletHandler.java:363)
at org.mortbay.jetty.security.SecurityHandler.handle(SecurityHandler.java:216)
at org.mortbay.jetty.servlet.SessionHandler.handle(SessionHandler.java:181)
at org.mortbay.jetty.handler.ContextHandler.handle(ContextHandler.java:712)
at org.mortbay.jetty.webapp.WebAppContext.handle(WebAppContext.java:406)
at org.mortbay.jetty.handler.ContextHandlerCollection.handle(ContextHandlerCollection.java:211)
at org.mortbay.jetty.handler.HandlerCollection.handle(HandlerCollection.java:114)
at org.mortbay.jetty.handler.HandlerWrapper.handle(HandlerWrapper.java:139)
at org.mortbay.jetty.Server.handle(Server.java:313)
at org.mortbay.jetty.HttpConnection.handleRequest(HttpConnection.java:506)
at org.mortbay.jetty.HttpConnection$RequestHandler.headerComplete(HttpConnection.java:830)
at org.mortbay.jetty.HttpParser.parseNext(HttpParser.java:514)
at org.mortbay.jetty.HttpParser.parseAvailable(HttpParser.java:211)
at org.mortbay.jetty.HttpConnection.handle(HttpConnection.java:381)
at org.mortbay.io.nio.SelectChannelEndPoint.run(SelectChannelEndPoint.java:396)
at org.mortbay.thread.BoundedThreadPool$PoolThread.run(BoundedThreadPool.java:442)
Caused by: java.lang.NullPointerException
at org.apache.myfaces.tomahawk.application.jsp.JspTilesViewHandlerImpl.renderView(JspTilesViewHandlerImpl.java:168)
at org.ajax4jsf.framework.ViewHandlerWrapper.renderView(ViewHandlerWrapper.java:101)
at org.ajax4jsf.framework.ajax.AjaxViewHandler.renderView(AjaxViewHandler.java:221)
at de.mindmatters.faces.lifecycle.RenderResponsePhase.executePhase(RenderResponsePhase.java:45)
... 21 more
my web.xml
<?xml version="1.0" encoding="UTF-8"?>
<web-app version="2.4" 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">
<context-param>
<param-name>contextConfigLocation</param-name>
<param-value>/WEB-INF/applicationContext.xml</param-value>
</context-param>
<context-param>
<param-name>com.sun.faces.verifyObjects</param-name>
<param-value>true</param-value>
<description>
Set this flag to true if you want the JSF
Reference Implementation to verify that all of the application
objects you have configured (components, converters,
renderers, and validators) can be successfully created.
Default value is false.
Poner a false cuando se ponga en produccion.
</description>
</context-param>
<context-param>
<param-name>com.sun.faces.validateXml</param-name>
<param-value>true</param-value>
<description>
Set this flag to true if you want the JSF
Reference Implementation to validate the XML in your
faces-config.xml resources against the DTD. Default
value is false.
Poner a false cuando se ponga en produccion.
</description>
</context-param>
<context-param>
<param-name>javax.faces.STATE_SAVING_METHOD</param-name>
<param-value>client</param-value>
<description>
Indica donde queremos guardar el estado de la aplicacion.
Poner a server cuando se ponga en produccion. antes probarlo!
</description>
</context-param>
<context-param>
<param-name>org.apache.myfaces.ALLOW_JAVASCRIPT</param-name>
<param-value>true</param-value>
<description>
Este parametro le dice a MyFaces si se va a permitir renderizar javascript.
Default: "true"
</description>
</context-param>
<context-param>
<param-name>org.apache.myfaces.PRETTY_HTML</param-name>
<param-value>true</param-value>
<description>
si es verdadero, el renderizado html estara formateado, permitiendo que se pueda leer
bien. En la fase de desarrollo, estara a true, cuando este en produccion, estara a false.
</description>
</context-param>
<session-config>
<session-timeout>
30
</session-timeout>
</session-config>
<welcome-file-list>
<welcome-file>
index.jsp
</welcome-file>
</welcome-file-list>

<listener>
<listener-class>org.springframework.web.context.request.RequestContextListener</listener-class>
</listener>
<listener>
<listener-class>org.springframework.web.context.ContextLoaderListener</listener-class>
</listener>
<servlet>
<servlet-name>Faces Servlet</servlet-name>
<servlet-class>javax.faces.webapp.FacesServlet</servlet-class>
<load-on-startup>1</load-on-startup>
</servlet>

<servlet>
<servlet-name>TilesServet</servlet-name>
<servlet-class>org.apache.struts.tiles.TilesServlet</servlet-class>
<init-param>
<param-name>definitions-config</param-name>
<param-value>/WEB-INF/tiles-defs.xml</param-value>
</init-param>
<load-on-startup>2</load-on-startup>
</servlet>
<servlet-mapping>
<servlet-name>Faces Servlet</servlet-name>
<url-pattern>*.jsf</url-pattern>
</servlet-mapping>
<filter>
<filter-name>MyFacesExtensionsFilter</filter-name>
<filter-class>org.apache.myfaces.webapp.filter.ExtensionsFilter</filter-class>
</filter>
</web-app>
tiles-defs.xml
<?xml version="1.0" encoding="ISO-8859-1" ?>
<!DOCTYPE tiles-definitions PUBLIC
"-//Apache Software Foundation//DTD Tiles Configuration 1.1//EN"
"http://jakarta.apache.org/struts/dtds/tiles-config_1_1.dtd">
<tiles-definitions>
<definition name="Base" path="/paginas/plantillaBasica.jsp">
<put name="titulo" value="Base" type="string"/>
<put name="cabecera" value="/cabecera.jsp" type="page"/>
<put name="cuerpo" value="base" type="page"/>
<put name="pie" value="base" type="page"/>
</definition>
<definition name="/busquedaDosCajas.tiles" extends="Base">
<put name="titulo" value="Busqueda con dos cajas" type="string"/>
<put name="cuerpo" value="/paginas/cuerpoDosCajas.jsp" type="page"/>
</definition>
</tiles-definitions>
faces-config.xml
<?xml version='1.0' encoding='UTF-8'?>
<!DOCTYPE faces-config PUBLIC
"-//Sun Microsystems, Inc.//DTD JavaServer Faces Config 1.1//EN"
"http://java.sun.com/dtd/web-facesconfig_1_1.dtd">

<faces-config>
<application>
<view-handler>org.apache.myfaces.tomahawk.application.jsp.JspTilesViewHandlerImpl</view-handler>
</application>

<application>
<variable-resolver>
org.springframework.web.jsf.DelegatingVariableResolver
</variable-resolver>
</application>

<application>
<locale-config>
<default-locale>es</default-locale>
</locale-config>
</application>

<navigation-rule>
<from-view-id>*</from-view-id>
<navigation-case>
<from-outcome>succesNoJS</from-outcome>
<to-view-id>/paginas/listado.jsp</to-view-id>
</navigation-case>
<navigation-case>
<from-outcome>error</from-outcome>
<to-view-id>error.jsp</to-view-id>
</navigation-case>
</navigation-rule>
</faces-config>
index.jsp
<%@ page session="false"%>
<%
response.sendRedirect("busquedaDosCajas.jsf");
%>
anybody could help me? i dont know whats happening
regards a lot

first make sure you are using Tiles stand-alone (in Struts Sandbox)
add the follwoing servlet to your web.xml
<servlet>
<servlet-name>Tiles Servlet</servlet-name>
<servlet-class>org.apache.tiles.servlet.TilesServlet</servlet-class>
<load-on-startup>1</load-on-startup>
</servlet>
add the following context-param to your web.xml
<context-param>
<param-name>tiles-definitions</param-name>
<param-value>/WEB-INF/tiles.xml</param-value>
</context-param>
add the following to your faces-config.xml
<view-handler>org.apache.shale.tiles.TilesViewHandler</view-handler>
add the following dependency to your pom.xml
<dependency>
<groupId>org.apache.shale</groupId>
<artifactId>shale-tiles</artifactId>
<version>1.0.3</version>
</dependency>
that should be it.
Khaled

Similar Messages

Jsf and tiles

hi all.
i'm developing an application using jsf and tiles.
i've some problem in the general layout page.
how can I refer to images and files,if I don't know where the page will be used?
with struts i've used <html:rewrite page=" ... " /> but it doesn't work with jsf.
I only use the TilesServlet.
any suggestion?
i've also try to define the url like "/css/mycss.css" but in local dosn't work.
thank a lot for any reply!

hi all.
i'm developing an application using jsf and tiles.
i've some problem in the general layout page.
how can I refer to images and files,if I don't know where the page will be used?
with struts i've used <html:rewrite page=" ... " /> but it doesn't work with jsf.
I only use the TilesServlet.
any suggestion?
i've also try to define the url like "/css/mycss.css" but in local dosn't work.
thank a lot for any reply!

Using JSF and tiles

Hi Friends,
I'm trying to combine JSF and tiles as follows:
Template file:
<f:subview id="content">
<tiles:insert attribute="content" flush="false"/>
</f:subview>
content file:
<tiles:insert definition="userSpecific">
<tiles:put name="content" type="string" >
<h:outputText value="aaaa"/>
</tiles:put>
</tiles:insert>
I get the following error when loading the content file:
2007-06-20 10:14:10,578 [http-8080-Processor23] ERROR org.apache.myfaces.shared_impl.taglib.UIComponentTagUtils - Component javax.faces.component.UIViewRoot is no ValueHolder, cannot set value.
I tried putting the template content in a verbatim tag and then it works
but the content page is not displayed in correct place in the template...
Thanks a lot in advance!

Are you dead set on using tiles? I can see tiles including JSF but JSF including tiles? Not sure if that will work.
My suggestion is to use Trinidad. It has the concept of Regions which is very "tiles" like and you will be far more successful.

Clarrification about JSF and JBoss Seam

Hi ,
i have just started a couple of hours ago reading about JSF and JBoss Seam and it seems interesting ......
here is my question :
i have a form ( registration form ) written in jsp and a congratulation page (jsp page too)
is right what i am saying ?
JSF form ( input values) are sent to Seam to be validated under hibernate rules and then it( Seam ) responses to the JSF the entity bean .
again JSF form asks Seam to resolve the variable Register ( the value of the submit button in the form) and Seam returns the RegisterACtion
After that the same jsp page invoke the register method of the RegisterAction stateless session beam .inside the register method it redirect the user to congratulation jsp page .
do you think its correct
sorry folks for my english
Best reagrds
yacine fandi

or maybe if you can give a link of a good tutorial I�ll be greatfull
cheers yacine
Message was edited by:
fandi_yacine

Issue in using JSF and tiles

Hai,
I am using JSF and tiles in my application along with richfaces 3.2 jar but the suggestion box does not work when i use incorporate tiles to the jsp page,Please help me out.Here is my code
Content Page
<%@ taglib prefix= "f" uri="http://java.sun.com/jsf/core"%>
<%@ taglib uri="http://java.sun.com/jsp/jstl/core" prefix="c" %>
<%@ taglib uri="http://java.sun.com/jsf/core"   prefix="f" %>
<%@ taglib uri="http://java.sun.com/jsf/html"   prefix="h" %>
<%@ taglib uri="http://jakarta.apache.org/tiles" prefix="tiles" %>
     <f:view >
         <link href="<%=request.getContextPath()%>\styles\Form.css" rel="stylesheet" type="text/css"/>
         <link href="<%=request.getContextPath()%>\styles\Menu.css" rel="stylesheet" type="text/css"/>
         <link href="<%=request.getContextPath()%>\styles\Header.css" rel="stylesheet" type="text/css"/>
         <title><h:outputText value="Brand"/></title>
         <h:form id="testForm">
             <tiles:insert definition="test_create" flush="false"/>
         </h:form>
     </f:view>JSP
<%@ taglib uri="http://java.sun.com/jsf/html" prefix="h"%>
<%@ taglib uri="http://java.sun.com/jsf/core" prefix="f"%>
<%@ taglib uri="http://richfaces.ajax4jsf.org/rich" prefix="rich"%>
<%@ taglib uri="https://ajax4jsf.dev.java.net/ajax" prefix="a4j"%>
<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
<html>
<head>
<meta http-equiv="Content-Type" content="text/html; charset=UTF-8">
<title>Insert title here</title>
</head>
<f:subview id="come">
<body>
<h:form>
<h:outputText value="Provider:" styleClass="SubTitle" />
<h:inputText value="#{testMBean.property}" size="25" id="dpiSuggest" styleClass="SubTitle">
    <a4j:support event="onkeyup" />
</h:inputText>
<rich:suggestionbox for="dpiSuggest" suggestionAction="#{testMBean.suggest}" height="180" width="180" var="suggest">
<h:column>
<h:outputText value="#{suggest.countryName}" />
</h:column>
<h:column>
<h:outputText value="#{suggest.countryCode}" />
</h:column>
</rich:suggestionbox>
</h:form>
</body>
</f:subview>
</html>
*tiles.xml*
<tiles-definitions>
    <definition name="header-menu-content" path="/layout/basicLayout.jsp">
        <put name="gridClass"           value="headerMenuContent"/>
        <put name="headerClass"         value="HeaderBgcolor"/>
        <put name="menuColumnClass"     value="MenuBorder"/>
        <put name="contentColumnClass" value="BodyBgColor"/>
    </definition>
    <definition name="home" extends="header-menu-content">
        <put name="header" value="/common/header.jsp"/>
        <put name="menu"    value="/common/menu.jsp"/>
        
        <put name="content" value="/common/home.jsp"/>
    </definition>
    <definition name="error" extends="header-menu-content">
        <put name="header" value="/common/header.jsp"/>
        <put name="menu"    value="/common/menu.jsp"/>
        
        <put name="content" value="/common/error.jsp"/>
    </definition>
        <definition name="test_create" extends="header-menu-content">
             <put name="header" value="/common/header.jsp" />
             <put name="menu" value="/common/menu.jsp" />
             
             <put name="content" value="/test.jsp" />
         </definition>
    <tiles-definitions>
*web.xml*
<?xml version="1.0" encoding="UTF-8"?>
<web-app version="2.5" xmlns="http://java.sun.com/xml/ns/javaee" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xsi:schemaLocation="http://java.sun.com/xml/ns/javaee http://java.sun.com/xml/ns/javaee/web-app_2_5.xsd">
    <session-config>
        <session-timeout>
            30
        </session-timeout>
    </session-config>
    <welcome-file-list>
        <welcome-file>welcome.jsp</welcome-file>
        </welcome-file-list>
         <context-param>
    <param-name>com.sun.faces.verifyObjects</param-name>
    <param-value>false</param-value>
</context-param>
<context-param>
    <param-name>com.sun.faces.validateXml</param-name>
    <param-value>true</param-value>
</context-param>
<context-param>
    <param-name>javax.faces.STATE_SAVING_METHOD</param-name>
    <param-value>client</param-value>
</context-param>
<servlet>
    <servlet-name>Faces Servlet</servlet-name>
    <servlet-class>javax.faces.webapp.FacesServlet</servlet-class>
    <load-on-startup>1</load-on-startup>
</servlet>
<servlet-mapping>
    <servlet-name>Faces Servlet</servlet-name>
    <url-pattern>*.faces</url-pattern>
</servlet-mapping>
<context-param>
<param-name>org.richfaces.SKIN</param-name>
<param-value>blueSky</param-value>
</context-param>
<filter>
<display-name>RichFaces Filter</display-name>
<filter-name>richfaces</filter-name>
<filter-class>org.ajax4jsf.Filter</filter-class>
</filter>
<filter-mapping>
<filter-name>richfaces</filter-name>
<servlet-name>Faces Servlet</servlet-name>
<dispatcher>REQUEST</dispatcher>
<dispatcher>FORWARD</dispatcher>
<dispatcher>INCLUDE</dispatcher>
</filter-mapping>
        <servlet>
      <servlet-name>Tiles Servlet</servlet-name>
      <servlet-class>org.apache.tiles.servlets.TilesServlet</servlet-class>
      <init-param>
         <param-name>definitions-config</param-name>
         <param-value>/WEB-INF/tiles.xml</param-value>
      </init-param>
      <load-on-startup>2</load-on-startup>
   </servlet>
    </web-app>
*facesconfig.xml*
<?xml version="1.0" encoding="UTF-8"?>
<faces-config version="1.2"
              xmlns="http://java.sun.com/xml/ns/javaee"
              xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
              xsi:schemaLocation="http://java.sun.com/xml/ns/javaee http://java.sun.com/xml/ns/javaee/web-facesconfig_1_2.xsd">
    <navigation-rule>
            <navigation-case> 
            <from-outcome>test</from-outcome>
            <to-view-id>/testContent.jsp</to-view-id>
            <redirect/>
        </navigation-case>
    </navigation-rule>
    <managed-bean>
        <managed-bean-name>testMBean</managed-bean-name>
        <managed-bean-class>testMBean</managed-bean-class>
        <managed-bean-scope>session</managed-bean-scope>
    </managed-bean>
</faces-config>Edited by: SreeramIyer on May 29, 2008 4:50 AM

Are you dead set on using tiles? I can see tiles including JSF but JSF including tiles? Not sure if that will work.
My suggestion is to use Trinidad. It has the concept of Regions which is very "tiles" like and you will be far more successful.

Jsf and tiles via myfaces

Greetings:
Please either confirm and/or correct following proposed solution for Myfaces tiles.
Issue: isert a tile definition and attribute in a pure jsf page.
First passed solution: A hybrid of Jsp programming and Jsf. I was able to create a tile page layout in pure jsf except in the portal columns i used old fashion jsp programming to insert a list of portletDefinitions which is extracted from jsf ValueBinding of its managed beans.
The problem with the above approach is that it works well only with html portlet fragments. When a portlet fragment has some jsf elements, the page rendering has conflict of simultaneous rendering between jsf and jsp. The portlet fragments are rendered in a woring place.
Proposed solution: use <h:dataTable ...> to render the portletList and extract the item portletDefinition as following:
<h:dataTable var="portlet"
value="#{portalTabbedBean.selectedPane.serviceListL}" >
<f:verbatim>
<h:outputText
value="<tiles:insert name=#{portlet.portletDefinition} flush='false' /> " />
</f:verbatim>
</h:dataTable>
Note on the name of tiles:insert element, which i just extracted the definition as a jsp variable to make it work in the first hybrid solution:
<tiles:insert name="<%=portletDefinition%>" flush="false" />
Thanks
BaTien
DBGROUPS

I reply this myself. Jsf and Jsp programming either via Jstl or while loop do not go together under current version.
I solve the problem by using Jsp programming and insert the portlet tile fragment directly rather than though a portlet template with different tile content attribute. The portlet tile is created as <h:panelGrid ...> and observe the set rules to make Jsf and jsp working together. Hopefully Jsf and Jsp will be able to work together nicely in their next specifications.

[ANNOUNCE] Exadel's Max Katz talks about JSF and AJAX

Hello,
I'm pleased to announce that JSF Central has just published an interview with Exadel senior systems engineer Max Katz. In the interview, Max talks about the key value and benefits of JSF, how it compares to other frameworks, why it is such a good fit for AJAX, and support for JSF technology at Exadel.
Here's a quote:
KM: What do you think is the key value of JSF?
MK: It's definitely the component-based approach to building web applications, and that it's a standard. JSF has introduced a new paradigm to web application development�building applications out of components. It allows developers to concentrate on application business logic rather than on little details of HTML and other plumbing that is common to all web applications.
Being a standard is very important for the community, and it helps vendors like Exadel create advanced visual tools. The component-based approach also gave rise to vendors building web components, which also benefits developers. Instead of spending two weeks on integrating a calendar feature into your application, you can now get a calendar component and concentrate on the business problem you're trying to solve.
KM: Let's talk about AJAX for a moment. What do you think makes JSF such a good fit for AJAX?
MK: It's the component approach that makes AJAX such a good fit for JSF. You develop your application out of JSF components that provide AJAX functionality. This approach hides all the complexity of JavaScript and XML. Developers don't need to work with error-prone JavaScript making sure it works in all browsers. The AJAX JSF components are tested, ready-to-use components. From the developer perspective, there is really no difference between using the commandButton standard component and using the JSF AJAX drag-and-drop components. The AJAX component is simply a lot more sophisticated in what it does. You can add AJAX functionality in a matter of minutes by using such components. It's very powerful.
To see the rest of the article, visit
http://www.jsfcentral.com/articles/katz-06-16-06.html.
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
Kito D. Mann
Author, JavaServer Faces in Action
http://www.virtua.com - JSF/Java EE consulting, training, and mentoring http://www.JSFCentral.com - JavaServer Faces FAQ, news, and info

The posted link led to a *404*.
I think I found the podcast and transcript under [article on JSFCentral.com|http://www.jsfcentral.com/listings/R2925?link] . Kito: is this the correct location?

[ANN] JSF and ADF Faces Q&A online session today

Join us for an online discussion and ask your questions about JSF and ADF Faces. Today (Thu) at 10:00am PST (California time).
http://www.oracle.com/technology/tech/java/newsletter/seminars.html

Great here are a few IF there is time:
1. How round trips will JSF and ADF Faces take upon initial page load? In other words, does the initial page load come with data already populated? This makes a difference for those of us who have data heavy pages with lots of lag. Currently with ADF - UIX it seems as though the page is loaded and then round trips are taken to populate the data in the page.
2. Is a JSF and ADF faces project in future versions of JDeveloper more easily/efficiently source controlled than current ADF/UIX projects?
3. What is the extent of the involvement of the struts framework in JSF and ADF Faces?
Thanks very much Shay.
-brian

JSF with TILES and HTML-Code

Hello!
I have a pure JSP-project using tiles. Now I want to migrate to JSF and find some problems.
When I use my existing layout and include the different JSPs I have no problem as long I have a single f:view in every jsp file is used. When I try to define f:view and a h:form including different files and in each file JSF componets where used I got a very bad result. Additiotal I have to say, that I try to keep my formatting with HTML tags existing.
The effect is, that all JSF componets were rendered at the beginning of the jsp file and than be included into the layout.
Have I use a special order of f:view, f:subview, h:form, ....
Alternative I could make a complete reprogramming of the JSP's, not my favourit, but than I need the possibility to set single formats for each <td> in a table and this seems not to be possible with h:panelGrid.
Havy anyone an idea?
Thanks for your help!

Read about facelets as a replacement for tiles in jsf.

JSF 1.2 and Tiles integration

I have a web application using JSF 1.1 and Tiles that I am trying to upgrade to run using JSF 1.2.
It is working as far as working out that it should use the tile, but then it all seems to fall over when trying to render.
Does anyone know if it is possible to use Tiles with JSF 1.2?
Steven

Hi,
I took the Shales TileViewHandler and replaced the renderView method with the one below. This is a copy of the method from the Sun RI except that it passes the tile (ComponentDefinition) along to the subsequent methods.
Then when it gets down to executePageToBuildView the requestURI is obtained from the tile (tile.getPath()) rather than from the UIViewRoot (viewToExecute.getViewId()).
   public void renderView(FacesContext facesContext, UIViewRoot viewToRender)
                                        throws IOException, FacesException {
      String viewId = viewToRender.getViewId();
      String tileName = getTileName(viewId);
      ComponentDefinition tile = getTile(tileName);
      if (log.isDebugEnabled()) {
         String message = null;
         try {
             message = bundle.getString("tiles.renderingView");
         } catch (MissingResourceException e) {
             message = "Rendering view {0}, looking for tile {1}";
         synchronized(format) {
            format.applyPattern(message);
            message = format.format(new Object[] { viewId, tileName });
         log.debug(message);
      if (tile != null) {
         if (log.isDebugEnabled()) {
            String message = null;
            try {
                message = bundle.getString("tiles.dispatchingToTile");
            } catch (MissingResourceException e) {
                message = "Dispatching to tile {0}";
            synchronized(format) {
               format.applyPattern(message);
               message = format.format(new Object[] { tileName });
            log.debug(message);
         dispatchToTile(facesContext, viewToRender, tile);
      else {
         if (log.isDebugEnabled()) {
            String message = null;
            try {
                message = bundle.getString("tiles.dispatchingToViewHandler");
            } catch (MissingResourceException e) {
                message = "Dispatching {0} to the default view handler";
            synchronized(format) {
               format.applyPattern(message);
               message = format.format(new Object[] { viewId });
            log.debug(message);
         defaultViewHandler.renderView(facesContext, viewToRender);
   private void dispatchToTile(FacesContext facesContext, UIViewRoot viewToRender, ComponentDefinition tile) throws java.io.IOException
       ExternalContext externalContext = facesContext.getExternalContext();
       Object request = externalContext.getRequest();
      Object context = externalContext.getContext();
      TilesContext tilesContext = TilesContextFactory.getInstance(context, request);
      ComponentContext tileContext = ComponentContext.getContext(tilesContext);
      if (tileContext == null) {
         tileContext = new ComponentContext(tile.getAttributes());
         ComponentContext.setContext(tileContext, tilesContext);
      else
         tileContext.addMissing(tile.getAttributes());
      renderTile(facesContext, viewToRender, tile);
      // dispatch to the tile's layout
      //externalContext.dispatch(tile.getPath());
   private void renderTile(FacesContext context, UIViewRoot viewToRender, ComponentDefinition tile) throws IOException, FacesException
       // suppress rendering if "rendered" property on the component is
       // false
       if (!viewToRender.isRendered()) {
           return;
       ExternalContext extContext = context.getExternalContext();
       ServletRequest request = (ServletRequest) extContext.getRequest();
       ServletResponse response = (ServletResponse) extContext.getResponse();
       try {
           if (executePageToBuildView(context, viewToRender, tile)) {
               response.flushBuffer();
               //ApplicationAssociate.getInstance(extContext).responseRendered();
               return;
       } catch (IOException e) {
           throw new FacesException(e);
       // set up the ResponseWriter
       RenderKitFactory renderFactory = (RenderKitFactory)
       FactoryFinder.getFactory(FactoryFinder.RENDER_KIT_FACTORY);
       RenderKit renderKit =
               renderFactory.getRenderKit(context, viewToRender.getRenderKitId());
       ResponseWriter oldWriter = context.getResponseWriter();
       initBuffSize(context);
       WriteBehindStringWriter strWriter =
             new WriteBehindStringWriter(context, bufSize);
       ResponseWriter newWriter;
       if (null != oldWriter) {
           newWriter = oldWriter.cloneWithWriter(strWriter);
       } else {
           newWriter = renderKit.createResponseWriter(strWriter, null,
                   request.getCharacterEncoding());
       context.setResponseWriter(newWriter);
       newWriter.startDocument();
       doRenderView(context, viewToRender);
       newWriter.endDocument();
       // replace markers in the body content and write it to response.
       ResponseWriter responseWriter;
       if (null != oldWriter) {
           responseWriter = oldWriter.cloneWithWriter(response.getWriter());
       } else {
           responseWriter = newWriter.cloneWithWriter(response.getWriter());
       context.setResponseWriter(responseWriter);
       strWriter.flushToWriter(responseWriter);
       if (null != oldWriter) {
           context.setResponseWriter(oldWriter);
       // write any AFTER_VIEW_CONTENT to the response
       writeAfterViewContent(extContext, response);
   private boolean executePageToBuildView(FacesContext context, UIViewRoot viewToExecute, ComponentDefinition tile)
   throws IOException {
       if (null == context) {
           String message = MessageUtils.getExceptionMessageString
                   (MessageUtils.NULL_PARAMETERS_ERROR_MESSAGE_ID, "context");
           throw new NullPointerException(message);
       if (null == viewToExecute) {
           String message = MessageUtils.getExceptionMessageString
                   (MessageUtils.NULL_PARAMETERS_ERROR_MESSAGE_ID, "viewToExecute");
           throw new NullPointerException(message);
       String mapping = Util.getFacesMapping(context);
       String requestURI =
             updateRequestURI(viewToExecute.getViewId(), mapping);
       String requestURI =
           updateRequestURI(tile.getPath(), mapping);
       if (mapping.equals(requestURI)) {
           // The request was to the FacesServlet only - no path info
           // on some containers this causes a recursion in the
           // RequestDispatcher and the request appears to hang.
           // If this is detected, return status 404
           HttpServletResponse response = (HttpServletResponse)
                 context.getExternalContext().getResponse();
           response.sendError(HttpServletResponse.SC_NOT_FOUND);
           return true;
       ExternalContext extContext = context.getExternalContext();
       // update the JSTL locale attribute in request scope so that JSTL
       // picks up the locale from viewRoot. This attribute must be updated
       // before the JSTL setBundle tag is called because that is when the
       // new LocalizationContext object is created based on the locale.
       // PENDING: this only works for servlet based requests
       if (extContext.getRequest()
       instanceof ServletRequest) {
           Config.set((ServletRequest)
           extContext.getRequest(),
                      Config.FMT_LOCALE, context.getViewRoot().getLocale());
       // save the original response
       Object originalResponse = extContext.getResponse();
       // replace the response with our wrapper
       ViewHandlerResponseWrapper wrapped =
             new ViewHandlerResponseWrapper(
                   (HttpServletResponse)extContext.getResponse());
       extContext.setResponse(wrapped);
       // build the view by executing the page
       extContext.dispatch(requestURI);
       // replace the original response
       extContext.setResponse(originalResponse);
       // Follow the JSTL 1.2 spec, section 7.4,
       // on handling status codes on a forward
       if (wrapped.getStatus() < 200 || wrapped.getStatus() > 299) {
           // flush the contents of the wrapper to the response
           // this is necessary as the user may be using a custom
           // error page - this content should be propagated
           wrapped.flushContentToWrappedResponse();
           return true;
       // Put the AFTER_VIEW_CONTENT into request scope
       // temporarily
       if (wrapped.isBytes()) {
           extContext.getRequestMap().put(AFTER_VIEW_CONTENT,
                                          wrapped.getBytes());
       } else if (wrapped.isChars()) {
           extContext.getRequestMap().put(AFTER_VIEW_CONTENT,
                                          wrapped.getChars());
       return false;
   }You will also find you need to copy a few other methods from the Sun RI.
There were a couple of calls to ApplicationAssociate.responseRendered() which I just commented out as well (because they are not visible). They stop people changing the StateManager or ViewHandler after responses have been rendered. Probably not a problem since I will have replaced the ViewHandler anyway.
Steven

Tiles, jsf and css

Hi,
I use JSF with Tiles for the first time to built a web application.
I have a problem with my stylesheet which I use for my layout and the other pieces of pages.
When I start my application, the first page works and the look and feel uses the stylesheet. But when I call an other page, the stylesheet isn't apply. I know there is a problem with the context path ...
For the moment, I declare my stylesheet like that :
<link rel="stylesheet" href="/css/style.css" type="text/css">
So, it works only the the first page.
I tried like this, thanks to the struts html tags :
<link rel="stylesheet" href="<html:rewrite page='/css/style.css'/>" type="text/css">
but this time, i have an error :
[ServletException in:/tiles/layout.jsp] org.apache.struts.taglib.html.MessagesTei'
If someone has a solution ...
thanks..

Will you please explain to me how you are doing CSS layout? I am having a problem with JSF 1.1 RI as everything is in a <td>. I want to get rid of these and change the rendered markup to output <div>s unless I can alter the location of <td>s on the page. This sounds like it would break the table model, so I doubt this is possible.
Thank you for any input,
TacoEater

Very big problem with JSF about FORM and "id=" for HTML form's elements and

I have discovered a very big problem with JSF about FORM and "id=" for HTML form's elements and java instruction "request.getParameterNames()".
Suppose you have something like this, to render some datas form a Java Beans :
<h:dataTable value="#{TablesDb2Bean.myDataDb2ListSelection}" var="current" border="2" width="50%" cellpadding="2" cellspacing="2" style="text-align: center">
<h:column>
<f:facet name="header">
<h:outputText value="Name"/>
</f:facet>
<h:outputText id="nameTableDb2" value="#{current.db2_name_table}"/>
</h:column>
</h:dataTable>
Everything works fine...
Suppose you want to get the name/value pairs for id="nameTableDb2" and #{current.db2_name_table} to process them in a servlet. Here is the HTML generated :
<td><span <span class="attribute-name">id=<span class="attribute-value">"j_id_jsp_1715189495_22:0:nameTableDb2">my-table-db2-xxxxx</span></td>
You think you can use the java instructions :
Enumeration NamesParam = request.getParameterNames();
while (NomsParam.hasMoreElements()) {
String NameParam = (String) NamesParam.nextElement();
out.println("<h4>"++NameParam+ "+</h4>);
YOU ARE WRONG : request.getParameterNames() wants the syntax *name="nameTableDb2" but JSF must use id="nameTableDb2" for "<h:outputText"... So, you can't process datas in a FORM generated with JSF in a Servlet ! Perhaps I have made an error, but really, I wonder which ?
Edited by: ungars on Jul 18, 2010 12:43 AM
Edited by: ungars on Jul 18, 2010 12:45 AM

While I certainly appreciate ejb's helpful responses, this thread shows up a difference in perspective between how I read the forum and how others do. Author ejb is correct in advising you to stay inside JSF for form processing if form processing is what you want to do.
However, I detect another aspect to this post which reminds me of something Marc Andreesen once said when he was trying to get Netscape off the ground: "there's no such thing as bad HTML."
In this case, I interpret ungar's request as a new feature request. Can I phrase it like this?
"Wouldn't it be nice if I could render my nice form with JSF but, in certain cases, when I REALLY know what I'm doing" just post out to a separate servlet? I know that in this case I'll be missing out on all the nice validation, conversion, l10n, i18n, ajax, portlet and other features provided by JSF".
If this is the case, because it really misses the point of JSF, we don't allow it, but we do have an issue filed for it
https://javaserverfaces-spec-public.dev.java.net/issues/show_bug.cgi?id=127
If you can't wait for it to be fixed, you could decorate the FormRenderer to fix what you want.
I have an example in my JSF book that shows how to do this decoration. http://bit.ly/edburnsjsf2
Ed

Blank Page with JSF 1.1.01 RI and Tiles

My web pages have been rendered without any problem using JSF 1.1 and Tiles with Weblogic 8.1 SP3. But it can't handle multiple forms within a page. So I upgraded JSF to version 1.1.01 RI. I only get blank pages since the upgrade.
Does anybody have the same problem? Any help is appreciated.

I have the same problem with Tomcat 5.5 and tried both 1.1.01 and 1.1.02. I used both JSF RI 1.0 and 1.1 with no problem on JSF with tiles, but because of the known bugs in 1.1 I had to use 1.1.01 or later which doesn't work nicely with tiles. Does anyone know how to fix this in Tomcat?

Simple question about JSF configuration

I am using Tomcat 5.0 in Windows XP SP2. When I create a web application with JSF and put it into {tomcat_home}\webapps\, everything works perfect. But when I add a context path in Tomcat's server.xml such like
<Context docBase="C:\works\java_projects\jsf_test" path="/jsf_test" reloadable="true" debug="0"/>
And then I put same web application into this context path and try the url like http://machinename:8080/jsf_test/test.faces, it gives me exception as follow
I wonder if anyone knows about that? Thanks a lot!!
type Exception report
message
description The server encountered an internal error () that prevented it from fulfilling this request.
exception
javax.servlet.ServletException: Servlet.init() for servlet Faces Servlet threw exception
     org.apache.catalina.authenticator.AuthenticatorBase.invoke(AuthenticatorBase.java:462)
     org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.java:118)
     org.apache.coyote.tomcat5.CoyoteAdapter.service(CoyoteAdapter.java:160)
     org.apache.coyote.http11.Http11Processor.process(Http11Processor.java:799)
     org.apache.coyote.http11.Http11Protocol$Http11ConnectionHandler.processConnection(Http11Protocol.java:705)
     org.apache.tomcat.util.net.TcpWorkerThread.runIt(PoolTcpEndpoint.java:577)
     org.apache.tomcat.util.threads.ThreadPool$ControlRunnable.run(ThreadPool.java:683)
     java.lang.Thread.run(Thread.java:595)
root cause
java.lang.NullPointerException
     javax.faces.webapp.FacesServlet.init(FacesServlet.java:144)
     org.apache.catalina.authenticator.AuthenticatorBase.invoke(AuthenticatorBase.java:462)
     org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.java:118)
     org.apache.coyote.tomcat5.CoyoteAdapter.service(CoyoteAdapter.java:160)
     org.apache.coyote.http11.Http11Processor.process(Http11Processor.java:799)
     org.apache.coyote.http11.Http11Protocol$Http11ConnectionHandler.processConnection(Http11Protocol.java:705)
     org.apache.tomcat.util.net.TcpWorkerThread.runIt(PoolTcpEndpoint.java:577)
     org.apache.tomcat.util.threads.ThreadPool$ControlRunnable.run(ThreadPool.java:683)
     java.lang.Thread.run(Thread.java:595)
note The full stack trace of the root cause is available in the Apache Tomcat/5.0.28 logs.
:

FacesServlet.init() processes only the followings: facesContextFactory = FactoryFinder.getFactory(FACES_CONTEXT_FACTORY);
applicationFactory = FactoryFinder.getFactory(APPLICATION_FACTORY);
application = applicationFactory.getApplication();
lifecycleFactory = FactoryFinder.getFactory(LIFECYCLE_FACTORY);
lifecycle = lifecycleFactory.getLifecycle(lifecycleId);NPE occurrs at the third line when it can't find ApplicationFactory.
Check how your container loads the class.

Is there an idiots guide to JSF and scope somewhere?

I am getting very confused with scope and JSF.
I have a page that just displays customer details (from CustomerBean extends Customer) with a button that should allow the user to change the customer details. Both pages use the same backing bean (is that recommended?).
customerDetail.jsp --> editCustomer.jsp
If I set the scope of CustomerBean to session, editCustomer sees the same customer as customerDetail. It seems to me that I shouldn't really be using session scope as I don't want a particular customer to hang around once I have finished with him. So what should I be doing?
Should customerBean be request scoped? If so how does editCustomer see it?
Or should I somehow destroy the session scoped customerBean when I have finished with it?
I also notice that some example jsps out there have a hidden field for the ID - should I simply look up the customer again from the database in editCustomer?
I also tried to add a <h:inputHidden value="#{customerBean}"/> but that broke my jsp.
I have bought and read the J2EE tutorial but I am still confused as to what the recommended way to drag the same Object through two jsp pages.
It's probably very simple but it's doing my head in ;-)
- David

Yeah, forming a model in your head to explain something can be painful, sometimes. This question has come up before, including where I work, and I've never really seen a comprehensive answer, so I'll just write one. :)
This is kind of a basic servlet concept, so I'll talk mostly about servlets. JSF is just flavor on top of this.
The lifetime of the request is: from the time the user hits "submit" until the time the response is fully rendered, whatever page that is.
So, you have a form the user has filled out and he/she hits "submit".
The HTTP POST request goes to the server (open port 80, write some "key: value" headers to satisfy the HTTP protocol requirements, followed by a stream of text that represents the users' form field values, wait for a response) which then proceeds to process it by parsing the incoming data and making a bunch of subroutine calls. The last set of subroutine calls basically involves a bunch of println() calls to write HTML into an output stream, which is the response the requesting browser is listening for. When that stream is done, the browser displays the html.
There's nothing that says the html that's displayed is the same as the html that originally held the form the user submitted. The first page is essentially garbage that somehow generated some form fields. The server could care less what it was, all it wants is the key=value pairs.
You could, if you were so inclined, code all those println()s yourself. That's straight servlet programming. It's totally under your control. You could code println( "<html><body>Hi, Mom!</body></html>"); and be done.
Or, you could write a JSP that, when compiled, turns into essentially a subroutine chock full o' println()s, and you could call that subroutine.
You do that with RequestDispatcher.forward(). It's just a subroutine call. (But don't do any more scribbling on the output stream after it returns, 'cause the stream's essentially been closed.)
It's all a big call tree with one thread of execution, single entry, single exit. One of the nice things about servlets is that the infrastructure makes available to you, in a contextual sorta way, the original request parameters plus whatever attributes you choose to attach to the request as your proceed w/your processing, kind of like charms on a charm bracelet (via ServletRequest.setAttribute()). (When I say "contextual", I mean the ServletRequest is passed in as a parameter to Servlet.service() so you can sling it around in your call tree.) Attributes you choose to attach while processing incoming form data are available later (for instance... in the subroutine that has all those println()s you so carefully coded up or allowed the JSP compiler to generate for you).
When the call tree is done (you've finally printed "</html>", marked the output stream "done" somehow and shipped all that HTML back out to the browser), the ServletRequest object that held the incoming form parameters plus whatever attribute cruft it accumulated is garbage collected. (I could write something poetic about Elysium and gamboling among daisies, but... nah.) So, the lifetime of that data associated w/the ServletRequest is the duration of that request-processing call tree.
JSF gives you a nice bunch of automatically-generated request attributes, corresponding to your request-scoped managed beans. It even very kindly transfers (via the value bindings) incoming form parameters into properties of beans which are attributed onto your ServletRequest, automagically.
So, if, in your JSP, you bind your form data to request-scoped bean properties (not the bean itself, but the bean's properties), those exact same bean properties will be visible on whatever JSP you eventually wind up on and it will be available to whatever intervening logic you code up ("Invoke Application" phase), and when the request is done, it all vanishes into thin air.
To be more specific to your question: yes, I believe it is recommended to have the same bean between pages. That's kind of the whole point. If you find yourself at the end of a request trying to destroy session data that was created at the beginning of that request, you should probably be using request scoping, not session.
I could be wrong, but I don't think you can bind an entire bean to an html element value. You bind bean properties. Of course, there's nothing to say that a bean property couldn't be... another bean!
In your particular case, I guess you have a bunch of display-only strings that come from your customer bean, plus a hidden "key" field somewhere. You could bind that hidden field to the customer.key property and Customer.setKey() would do whatever's necessary to get the rest of the data into the bean. That could be a d/b lookup or a map or array (cache) fetch. Or you could have a "current customer" in your session (that would have to be session-scoped, because you paint the detail screen w/one request and then paint the "edit" screen w/the same customer but in a different request). That "current customer" concept might cause you some problems later when you go multi-window or multi-frame in your webapp (truuuuuuuust me).
Also, I'm not sure why you need a CustomerBean separate from Customer. Can you just make Customer a bean and be done with it?
Holy cow, what an essay this turned out to be.
John Lusk.

About jsf and tiles

Similar Messages

Maybe you are looking for