ansaurus

Question

JSF tags not rendered

Answer 1

A:

Try:

<?xml version="1.0" encoding="ISO-8859-1" ?>

<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd"&gt;
<html xmlns="http://www.w3.org/1999/xhtml" xmlns:f="http://java.sun.com/jsf/core" xmlns:h="http://java.sun.com/jsf/html"&gt;
<head>
<meta http-equiv="Content-Type" content="text/html; charset=ISO-8859-1" />
<title>Example</title>
</head>
<body>
<f:view>
 <h:form>
    Some random data: <h:inputText/><br/>  <!-- Textfield ignored -->
    Some other data: <h:inputText/><br/>   <!-- Textfield ignored -->

    </h:form>

</f:view>
</body>
</html>

I've included the JSF <f:view> tag

StudiousJoseph 2010-07-25 16:52:42

This won't help. He's using Facelets where `f:view` isn't mandatory, not JSP. And even then, if he was using JSP, a missing `f:view` would have caused JSF to throw an `IllegalStateException` when it encounters a component without a parent `UINamingContainer` component during parsing.

BalusC 2010-07-26 02:42:03

Answer 2

A:

The symptoms of the JSF components not being parsed at all indicates that the FacesServlet hasn't run. This will happen when the request URL doesn't match the url-pattern of the FacesServlet as definied in web.xml. This would mean that the actual url-pattern of the FacesServlet isn't *.xhtml at all. Are you looking into and editing the right web.xml you think you are? Is the right web.xml been deployed with the webapp into the servletcontainer?

BalusC 2010-07-26 02:45:07

Answer 3

A:

Man, you haven't set the javax.faces.DEFAULT_SUFFIX context parameter. The default for jsf is jsp, so jsf will search for example.jsp instead of example.xhtml. Basically JSF replaces the extension of the resource requested with the javax.faces.DEFAULT_SUFFIX.

Use the following and it will work:

<context-param>
    <param-name>javax.faces.DEFAULT_SUFFIX</param-name>
    <param-value>.xhtml</param-value>
</context-param>

Petar Minchev 2010-07-27 06:29:07

This is true when you're using JSF 1.2 instead of 2.0, but it would have resulted in a 404 when passed through `FacesServlet`, not in an unparsed page. So it can only mean that it's not been passed through `FacesServlet`.

BalusC 2010-07-27 12:59:40

@BalusC Yes, but he hasn't told us which version of JSF is using. Also he hasn't clarified what he means by rendered. Maybe he gets a 404 and he hasn't told us. This is what I consider.

Petar Minchev 2010-07-27 13:04:41

Answer 4

A:

Do you have faces-config.xml in place that declares Facelets as view handler?

<?xml version="1.0"?>
<faces-config 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" version="1.2">
<application>
    <view-handler>com.sun.facelets.FaceletViewHandler</view-handler>
</application>
</faces-config>

Don't forget about javax.faces.DEFAULT_SUFFIX parameter to be set to .xhtml as mentioned above.

Martin 2010-07-27 12:35:55

ansaurus

tags:

views:

answers:

JSF tags not rendered

related questions