JSF 1.2 and

Hello!
I used MyFaces + Facelets and have no problems with After switching to JSF 1.2_01 I getting this strange error:
XML Parsing Error: undefined entity
Location: http://boris.nikom.ru:8080/test.jsf
Line Number 16, Column 14: <tr><td> </td></tr>
The original file looks like (please note I use   not directly):
<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd">
<html xmlns="http://www.w3.org/1999/xhtml"
xmlns:ui="http://java.sun.com/jsf/facelets"
xmlns:h="http://java.sun.com/jsf/html"
xmlns:t="http://myfaces.apache.org/tomahawk">
<head>
<meta http-equiv="Content-Type" content="text/html; charset=utf-8" />
<head>
<link rel="STYLESHEET" type="text/css" href="/css/style.css"/>
</head>
</head>
<body>
<table>
<tr><td> </td></tr>
</table>
</body>
</html>
My enviroment is: Resin 3.0.20, JSF 1.2_01, Facelets 1.1.11
WEB-INF/lib context:
commons-beanutils-1.7.0.jar commons-logging-1.0.4.jar
commons-codec-1.3.jar el-api.jar
commons-collections-3.1.jar el-ri.jar
commons-digester-1.6.jar jsf-api.jar
commons-el-1.0.jar jsf-facelets.jar
commons-fileupload.jar jsf-impl.jar
commons-lang-2.1.jar

Hello!
Detailed explanation of problem:
1) FireFox send HTTP Accept header with text/xml,application/xml,application/xhtml+xml ... etc
2) JSF 1.2 returns Content-Type: application/xhtml+xml
3) Based on the return type FireFox tries to validate XML and fails.
MyFaces always returns content-type text/html. So, question to gurus - is this correct behavior of JSF 1.2 or should be reported as bug?
With respect,
Boris

Similar Messages

Tomcat 6.0.9 and jsf 1.2 and jstl 1.2 using *.tag file error

I using :tomcat 6.0.9 and jsf 1.2 and jstl 1.2
My web.xml is at version 2.5 and I am using a custom tag (with the .tag extension). I am trying to use the http://java.sun.com/jsf/html library and values from my attribute. I'm new to this so I figure I must just me missing something.
I am run http://192.168.1.1/test.jsf laster,view:
HTTP Status 500 -
type Exception report
message
description The server encountered an internal error () that prevented it from fulfilling this request.
exception
org.apache.jasper.JasperException: Unable to compile class for JSP:
Stacktrace:
     org.apache.jasper.compiler.DefaultErrorHandler.javacError(DefaultErrorHandler.java:85)
     org.apache.jasper.compiler.ErrorDispatcher.javacError(ErrorDispatcher.java:330)
     org.apache.jasper.compiler.JDTCompiler.generateClass(JDTCompiler.java:415)
     org.apache.jasper.compiler.Compiler.compile(Compiler.java:308)
     org.apache.jasper.compiler.Compiler.compile(Compiler.java:286)
     org.apache.jasper.compiler.Compiler.compile(Compiler.java:273)
     org.apache.jasper.JspCompilationContext.compile(JspCompilationContext.java:566)
     org.apache.jasper.servlet.JspServletWrapper.loadTagFile(JspServletWrapper.java:212)
     org.apache.jasper.compiler.TagFileProcessor.loadTagFile(TagFileProcessor.java:576)
     org.apache.jasper.compiler.TagFileProcessor.access$000(TagFileProcessor.java:50)
     org.apache.jasper.compiler.TagFileProcessor$TagFileLoaderVisitor.visit(TagFileProcessor.java:627)
     org.apache.jasper.compiler.Node$CustomTag.accept(Node.java:1507)
     org.apache.jasper.compiler.Node$Nodes.visit(Node.java:2336)
     org.apache.jasper.compiler.Node$Visitor.visitBody(Node.java:2386)
     org.apache.jasper.compiler.TagFileProcessor$TagFileLoaderVisitor.visit(TagFileProcessor.java:631)
     org.apache.jasper.compiler.Node$CustomTag.accept(Node.java:1507)
     org.apache.jasper.compiler.Node$Nodes.visit(Node.java:2336)
     org.apache.jasper.compiler.Node$Visitor.visitBody(Node.java:2386)
     org.apache.jasper.compiler.Node$Visitor.visit(Node.java:2392)
     org.apache.jasper.compiler.Node$Root.accept(Node.java:489)
     org.apache.jasper.compiler.Node$Nodes.visit(Node.java:2336)
     org.apache.jasper.compiler.TagFileProcessor.loadTagFiles(TagFileProcessor.java:645)
     org.apache.jasper.compiler.Compiler.generateJava(Compiler.java:190)
     org.apache.jasper.compiler.Compiler.compile(Compiler.java:306)
     org.apache.jasper.compiler.Compiler.compile(Compiler.java:286)
     org.apache.jasper.compiler.Compiler.compile(Compiler.java:273)
     org.apache.jasper.JspCompilationContext.compile(JspCompilationContext.java:566)
     org.apache.jasper.servlet.JspServletWrapper.service(JspServletWrapper.java:308)
     org.apache.jasper.servlet.JspServlet.serviceJspFile(JspServlet.java:320)
     org.apache.jasper.servlet.JspServlet.service(JspServlet.java:266)
     javax.servlet.http.HttpServlet.service(HttpServlet.java:803)
     com.sun.faces.context.ExternalContextImpl.dispatch(ExternalContextImpl.java:414)
     com.sun.faces.application.ViewHandlerImpl.executePageToBuildView(ViewHandlerImpl.java:455)
     com.sun.faces.application.ViewHandlerImpl.renderView(ViewHandlerImpl.java:139)
     com.sun.faces.lifecycle.RenderResponsePhase.execute(RenderResponsePhase.java:108)
     com.sun.faces.lifecycle.LifecycleImpl.phase(LifecycleImpl.java:266)
     com.sun.faces.lifecycle.LifecycleImpl.render(LifecycleImpl.java:159)
     javax.faces.webapp.FacesServlet.service(FacesServlet.java:245)
note The full stack trace of the root cause is available in the Apache Tomcat/6.0.9 logs.
if go to /WEB-INF/tags/test.tag ,delete line: <h:outputText id="test" value="hello!" />
run http://192.168.1.1/test.jsf is OK!(no error),So I guess error for "<h:outputText id="test" value="hello!" />" line ,why in test.tag file do can't use the "http://java.sun.com/jsf/html " library,please help me.......
Here is file WEB-INF/web.xml content:
<?xml version="1.0" encoding="ISO-8859-1"?>

<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_5.xsd"
version="2.5">
<display-name>Welcome to Tomcat</display-name>
<description>
Welcome to Tomcat
</description>

<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>*.jsf</url-pattern>
</servlet-mapping>
</web-app>
Here is file /test.jsp code:
<%@ page contentType="text/html;charset=UTF-8" %>
<%@ taglib prefix="tags" tagdir="/WEB-INF/tags" %>
<%@ 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" %>
<f:view>
<html>
<head>
<title>test</title>
</head>
<body>

<h:outputText id="myinfo" value="test success" />
<tags:test/>

</body>
</html>
</f:view>
Here is file /WEB-INF/tags/test.tag code:
<%@tag pageEncoding="UTF-8"%>
<%@taglib prefix="f" uri="http://java.sun.com/jsf/core"%>
<%@taglib prefix="h" uri="http://java.sun.com/jsf/html"%>
<h:outputText id="test" value="hello!" />
Thanks for any help.

Don't know if it's important, but there is no schema avaiable at: http://java.sun.com/xml/ns/j2ee/web-app_2_5.xsd
I found the right one at: http://java.sun.com/xml/ns/javaee/web-app_2_5.xsd
/perty
Message was edited by:
perajonsson

Jsf newbie :: converter and navigation issues

Hi,
Iam facing a problem in my first jsf application.
Iam using jsf 1.1 and tomcat 5.5.7
I have a UserBean with a single attribute userName (which has public getter and setter methods).
* I have an index.jsp that redirects to login.faces.
* I have the appropriate servlet url-mapping in my web.xml that maps *.faces to the FacesServlet
Here's the code for login.jsp
<f:view>
   <h:form>
         <h3>Please enter your name </h3>
     <table>
      <tr>
        <td>Name:</td>
        <td><h:inputText id = "name" value="#{user.userName}"/></td>
     </tr>
     </table>
     <p><h:commandButton value="Login" action="welcome"/>
     </p>
     </h:form>
   </body>
</f:view>Next I have a welcome.jsp which simply outputs Hello <userName>
<f:view>
<h:form>
     <h:outputText value="#{user.userName}"></h:outputText>
</h:form>
</f:view>And this is my faces-config.xml
<?xml version="1.0"?>
<!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>
     <managed-bean>
          <managed-bean-name>user</managed-bean-name>
          <managed-bean-class>com.myjsf.UserBean</managed-bean-class>
          <managed-bean-scope>session</managed-bean-scope>
     </managed-bean>
     <navigation-rule>
          <from-view-id>/index.jsp</from-view-id>
          <navigation-case>
               <from-outcome>welcome</from-outcome>
               <to-view-id>/welcome.jsp</to-view-id>
          </navigation-case>
     </navigation-rule>
</faces-config>Now when I start my application , the index page redirects me to login.faces. I believe the FacesServlet intercepts this call, strips of .faces and forwards to login.jsp. Login.jsp is displayed correctly, so far so good. However from here on, I have all kinds of problems
1. Should the <from-view-id> be /index.jsp (my actual url) or /login.jsp (the url to which index.jsp forwards me to). Actually both seem to work (or not work depending on how you look at it :( )
2. Anyways whatever I set it to, the login.jsp is displayed correctly. The action attribute of the commandButton tag is set to 'welcome' which matches with the <from-outcome> value in navigation rule in faces-config.xml and I would have expected the welcome.jsp to load on form submit.
But the form just reloads itself on clicking submit.
I googled around and discovered that this may be due to validation errors or conversion errors and adding <h:messages/> would indicate the error source. AQccordingly I added it and got this o/p
" "name": " Conversion Error setting value 'Duke' for 'null Converter'. To cut a long agony story short, I found that I have to define a converter for some data types for validation and/or display. But all I have is a String property. Doesnt jsf provide a default Converter ?
3. I couldnt get my app to work when I put my jsps in a folder and access them as /<foldername>/jsp in my faces-config.xml. Isnt this possible ? Should all jsps be under the root folder ?
Will be thankful for any help.
cheers,
ram.
2. Whenever I click on

Thanks for the reference , I shall definitely go through it.
My immediate concern is to get the first program working.
Here is my source code for the bean.
package com.myjsf;
import java.io.Serializable;
public class UserBean implements Serializable {
    private String userName;
    public String getUserName() {
        return userName;
    public void setName(String userName) {
        this.userName = userName;
}Here's my login.jsp which comes up fine
<f:view>
   <h:form>
     <h:messages/>
         <h3>Please enter your name.</h3>
             Name: <h:inputText id = "userName" value="#{user.userName}"/><br>
              <h:commandButton value="Login" action="welcome"/>
     </h:form>
</f:view>Here's my faces-config.xml
<faces-config>
     <managed-bean>
          <managed-bean-name>user</managed-bean-name>
          <managed-bean-class>com.myjsf.UserBean</managed-bean-class>
          <managed-bean-scope>session</managed-bean-scope>
     </managed-bean>
     <navigation-rule>
          <from-view-id>/login.jsp</from-view-id>
          <navigation-case>
               <from-outcome>welcome</from-outcome>
               <to-view-id>/welcome.jsp</to-view-id>
          </navigation-case>
     </navigation-rule>
</faces-config>     And this is the error that I get
"userName": Conversion error occurred. The page gets displayed again. One thing I noticed was that in the html - view source the action attribute of the form tag is set to /myjsf/faces/login.jsp. Shouldnt it be welcome.jsp rather ?
Iam at my wits end. I have decided to write a Converter which may solve my problem, but is it required ?
Please help.
Thanks,
Ram.

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

JSF, tiles, xml and xsl

Good days people, I am employed at an app that wants to integrate JSF, tiles, xml and xsl.
Basically the app receives information of the user's interfaz, builds an url with the above mentioned information and invokes to a service web that a xml returns with the information. The idea is to generate the exit in format html or wml with an insole(staff) xsl and to send the result in this format to every jsp that is going to form a part of the page that it will generate tiles. at first I understand that it is feasible, i�d like to know if someone already has done it and since it has done it.
Just now what I have is a managed bean that receives the parameters of the altar frontal and invokes a method of a service, like this:
public String encuentra(){
//deja los atributos privados rellenos.
String mensaje ;
crearYRellenarBusquedaVO();
try {
setResultado(this.getServicio().obtenerResultadosWML(this.getBusquedaVO()));
mensaje="succesNoJS";
}catch(java.lang.IllegalArgumentException e){
mensaje="error";
}catch(es.yell.frontlite.exceptions.SrvBusquedaNoxtrumServiceException e1){
mensaje="error";
}catch(Exception e2){
mensaje="error";
return mensaje;
public String obtenerResultadosWML(es.yell.frontlite.service.impl.BusquedaVO busquedaVO){
if (busquedaVO == null){
throw new IllegalArgumentException(
"obtenerResultadosJSdesactivado(es.yell.frontlite.service.impl.BusquedaVO busquedaVO) - 'busquedaVO' no puede ser nulo.");
try{
return this.manejarObtenerResultadosWML(busquedaVO);
}catch(es.yell.frontlite.exceptions.SrvBusquedaNoxtrumServiceException e1){
throw new es.yell.frontlite.exceptions.SrvBusquedaNoxtrumServiceException(
"Error ejecutando el servicio String obtenerResultadosJSdesactivado(es.yell.frontlite.service.impl.BusquedaVO busquedaVO). " + e1.getCause(),e1);
}catch(Exception e){
throw new es.yell.frontlite.exceptions.SrvBusquedaNoxtrumServiceException(
"Error ejecutando el servicio String obtenerResultadosJSdesactivado(es.yell.frontlite.service.impl.BusquedaVO busquedaVO). " + e.getCause(),e);
//it returns html code!
protected String manejarObtenerResultadosWML(es.yell.frontlite.service.impl.BusquedaVO busquedaVO)
throws java.lang.Exception{
try{
// xmlOrigen has full xml response from server
String xmlOrigen = manejarObtenerResultadosJSActivado(busquedaVO);
Source xmlSource = new StreamSource(new StringBufferInputStream(xmlOrigen));
Source xsltSource = new StreamSource(SrvBusquedaNoxtrumServiceImpl.class.getResourceAsStream(Constantes.XSL_FILE));
StringWriter cadenaSalida = new StringWriter();
Result bufferResultado = new StreamResult(cadenaSalida);
TransformerFactory factoriaTrans = TransformerFactory.newInstance();
Transformer transformador = factoriaTrans.newTransformer(xsltSource);
transformador.transform(xmlSource, bufferResultado);
System.out.println(cadenaSalida.toString());
return cadenaSalida.toString();
}catch(Exception e2){
throw new es.yell.frontlite.exceptions.SrvBusquedaNoxtrumServiceException (e2.getMessage());
With this exit in html, since(as,like) how could i forward it towards a jsp especially?
faces-config.xml
<navigation-rule>
<from-view-id>/index.jsp</from-view-id>
<navigation-case>
<from-outcome>succesNoJS</from-outcome>
<to-view-id>/jsDesactivado.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>
index.jsp
<%@ taglib uri="http://java.sun.com/jsf/html" prefix="h" %>
<%@ taglib uri="http://java.sun.com/jsf/core" prefix="f" %>
<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
<html>
<f:view>
<f:loadBundle basename="MessageResources" var="msg"/>
<head>
<title>
${msg.titulo}
</title>
</head>
<body>
<h:form id="formulario">
Que:
<h:inputText id="campoQue" value="#{yellProxy.campoQue}" />
Donde
<h:inputText id="campoDonde" value="#{ yellProxy.campoDonde}" />
<h:commandButton id="boton" value="Encuentra" action="#{yellProxy.encuentra}"/>
</h:form>
</f:view>
</body>
</html>
jsDesactivado.jsp
<%@page contentType="text/html"%>
<%@page pageEncoding="UTF-8"%>
<%--
The taglib directive below imports the JSTL library. If you uncomment it,
you must also add the JSTL library to the project. The Add Library... action
on Libraries node in Projects view can be used to add the JSTL 1.1 library.
--%>
<%--
<%@taglib uri=" http://java.sun.com/jsp/jstl/core" prefix="c"%>
--%>
<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN"
" http://www.w3.org/TR/html4/loose.dtd">
<html>
<head>
<meta http-equiv="Content-Type" content="text/html; charset=UTF-8">
<title>JSP Page</title>
</head>
<body>
<h1>JSP Page</h1>
jsDesactivado!!
<%--
This example uses JSTL, uncomment the taglib directive above.
To test, display the page like this: index.jsp?sayHello=true&name=Murphy
--%>
<%--
<c:if test="${param.sayHello}">

Hello ${param.name}!
</c:if>
--%>
<jsp:getProperty name="yellProxy" property="resultado"/>
</body>
</html>
If you could pass me a simple example of use of an app that uses JSF, tiles, xml and xsl, i�be grateful
regards a lot!

We too (at Viking Freight) would also be very interested to see if anybody
has produced such a useful series of classes...
Frank Lees, Developer
-----Original Message-----
From: Amin, Kamran [mailto:kamran.aminframeworkinc.com]
Sent: Wednesday, January 19, 2000 12:11 PM
To: 'Forte User'
Subject: (forte-users) XML and XSL in Forte
Has anybody integrated an XSL parser with Forte. I know Forte provides us
with an XML parser but that does not help with parsing XSL. There a lot of
parsers written in JAVA but that will not integrate well with Forte. We
need something that will be easy to integrate with Forte. This parser will
take our XML and XSL to give us a result set. If anybody can comment on the
subject or share some information I would appreciate it.
thanks in advance.
ka
For the archives, go to: http://lists.sageit.com/forte-users and use
the login: forte and the password: archive. To unsubscribe, send in a new
email the word: 'Unsubscribe' to: forte-users-requestlists.sageit.com

JSF 1.2 and Weblogic 10.3.6 compatibility issue

Hi All,
Our application have been developed in JSF 1.2 and spring DAO. We have deployed it on Weblogic 10.3.6 X86 server.
We are facing an issue like on page load data are populated in the page. Say for example on page load company list getting populated and displayed in the drop down.
If we do any operation like select a company code or submit the page all the data are flushed out from the pages. After that navigation of pages also doesnot work.
We neither get any logs nor exception.
And i am not getting this issue in my local weblogic server - 10.3.5
We are struggling with this issue for more than 10 days now and its critical time for us to fix it ASAP.
Thanks,
Seetha

Hi kalyan,
We are not getting any logs. the control is going to javascript but the page get refreshed and all data are just vanishing.
We have tried to add below entries in weblogic-application.xml
<wls:prefer-application-packages>
<wls:package-name>com.sun.facelets.*</wls:package-name>
<wls:package-name>com.sun.faces.*</wls:package-name>
<wls:package-name>javax.faces.*</wls:package-name>
<wls:package-name>javax.servlet.*</wls:package-name>
</wls:prefer-application-packages>
No change.
Tried this
<wls:library-ref>
<wls:library-name>jsf</wls:library-name>
<wls:specification-version>1.2</wls:specification-version>
<wls:implementation-version>1.2</wls:implementation-version>
<wls:exact-match>false</wls:exact-match>
</wls:library-ref>
No Change.
tried this
<wls:prefer-application-resources>
<wls:resource-name>APP-INF/lib</wls:resource-name>
</wls:prefer-application-resources>
No Change
Anything we missing here. Why it is working in my local server and not in Integration server?
Kindly help us.
Thanks,
Seetha

JSF 1.2 and SQJ injection

Hi members;
I am using JSF 1.2 with iBATIS as DAO layer, I wonder if the only way to avoid sql injection in my application is to write some code (either JavaScript or Java code) to reject all risky charaters before sending it to the DAO, is there another way at the JSF components .
Regards

Don't bother with JavaScript cause it can be override.
If you're getting data from a backend database, you can use PreparedStatement (use with normal SQL statements) or CallableStatement (use with stored procedures) from Java's java.sql class. These methods can be easily integrated into your DAO class of your JSF project.
And, if you're still paranoid after using the above methods, you can try to supplement the above methods with regex expressions to only accept white-list data i.e. data that can be executed in your database without causing you any harm.

JSF 1.2 and JSTL 1.2

Now that JSF 1.2 and JSTL 1.2 both use the new unified EL is it possible to use them together? I know they could be used together before but it was discouraged. I'm mostly interested in the functions and the loops (although Trinidad seems to be working pretty well).

Thanks... I have switched over to facelets but I am getting the same problem:
<ui:composition template="./../WEB-INF/layout.xhtml">
   <ui:define name="menu">
           <ui:include src="./flightMenu.xhtml" />
   </ui:define>
   <ui:define name="content">
     <h:panelGrid border="0" columns="1" style="width:100%">
        <h:form>
          <rich:tabPanel switchType="ajax"
              valueChangeListener="#{flightBean.flightTabPanel.valueChanged}"
              binding="#{flightBean.flightTabPanel.tabPanel}" id="tab_panel">
              <f:valueChangeListener type="org.richfaces.TabChangeListener" />
              <rich:tab name="test" label="test">
                      <h:outputText value="bla bla" />
              </rich:tab>
              <ui:repeat var="tabb" value="#{flightBean.flightTabs}">
                      <rich:tab name="#{tabb.fltNum}" >
                              <h:outputText value="bla bla" />
                      </rich:tab>
              </ui:repeat>
          </rich:tabPanel>
        </h:form>
     </h:panelGrid>
   </ui:define>
</ui:composition>The probem is that the tabb.fltNum method is not being invoked... If anyone has been able to build dynamic tabs using RichFaces using a similar approach I will like to see how you did it...
BRgds, Paul

JSF datatable - any difference with JSF 1.1 and JSF 1.2

Hi All,
In my project there are lot of Datatables, which retrieve data from the database and display it to the user. For each datatable, the columns are not fixed. I want to create some kind of component that can be reusable.
It is basically a JSF portlet. Now i have to use RAD 6. RAD 6 supports only JSF1.1. I have to migrate this to RAD7 in the near future. Are there any differences between the Datatable in JSF 1.1 and JSF 1.2?
I had this approach in mind.
a) Create the datatable programmatically and put the contents to panelgrid. This way the jsp code will be minimized. Is it a good option.? Are the APIs same in both the versions?
b) Is it possible to create a custom datatable which can take some key as input. Then based on the key the datatable can be populated with as many columns as desired.
Please let me know if there are any other good options.
~Anitha.

Hi guys,
my code goes like this..
for (int j = 0; j < size; j++) {
               UIColumn column = new UIColumn();
               dataTable.getChildren().add(column);
               HtmlOutputText header = new HtmlOutputText();
               header.setValue(periodHeader[j]);
               column.setHeader(header);
               HtmlOutputText output = new HtmlOutputText();
               output.setValue(new Double(periodLiability[j]));
               ValueBinding vb1 = FacesContext.getCurrentInstance()
                         .getApplication().createValueBinding(
                                   ("#{liability.periodLiability["+j+"]}"));
               output.setValueBinding("value", vb1);
               column.getChildren().add(output);
this code gives me the number of headers i need. But, it doesnt render the columns. I have an array of Double (periodLiability) which stores few values of Double type. I want to show thesee values inthe dataTable Column.
Please help me..

JSF 1.2 and Tomcat 6.0.16, error parsing 'jsf-ri-runtime.xml'

I am working on an application that used jsf 1.1 but would like to move to jsf 1.2. I've added the 1.2 jars (jsf-api.jar and jsf-impl.jar) and jstl-1.2.jar to the app. When I deploy to tomcat 6, i get the following error:
15-Feb-2008 11:30:36 org.apache.catalina.core.StandardContext listenerStart
SEVERE: Exception sending context initialized event to listener instance of class com.sun.faces.config.ConfigureListener
com.sun.faces.config.ConfigurationException: CONFIGURATION FAILED! Unable to parse document 'jar:file:/C:/servers/apache-tomcat-6.0.16/webapps/myWebApp/WEB-INF/lib/jsf-impl-1.2.jar!/com/sun/faces/jsf-ri-runtime.xml': This parser does not support specification "null" version "null"
at com.sun.faces.config.ConfigManager.initialize(ConfigManager.java:212)
at com.sun.faces.config.ConfigureListener.contextInitialized(ConfigureListener.java:174)
at org.apache.catalina.core.StandardContext.listenerStart(StandardContext.java:3843)
at org.apache.catalina.core.StandardContext.start(StandardContext.java:4350)
at org.apache.catalina.core.ContainerBase.addChildInternal(ContainerBase.java:791)
at org.apache.catalina.core.ContainerBase.addChild(ContainerBase.java:771)
at org.apache.catalina.core.StandardHost.addChild(StandardHost.java:525)
at org.apache.catalina.startup.HostConfig.deployWAR(HostConfig.java:829)
at org.apache.catalina.startup.HostConfig.deployWARs(HostConfig.java:718)
at org.apache.catalina.startup.HostConfig.deployApps(HostConfig.java:490)
at org.apache.catalina.startup.HostConfig.start(HostConfig.java:1147)
at org.apache.catalina.startup.HostConfig.lifecycleEvent(HostConfig.java:311)
at org.apache.catalina.util.LifecycleSupport.fireLifecycleEvent(LifecycleSupport.java:117)
at org.apache.catalina.core.ContainerBase.start(ContainerBase.java:1053)
at org.apache.catalina.core.StandardHost.start(StandardHost.java:719)
at org.apache.catalina.core.ContainerBase.start(ContainerBase.java:1045)
at org.apache.catalina.core.StandardEngine.start(StandardEngine.java:443)
at org.apache.catalina.core.StandardService.start(StandardService.java:516)
at org.apache.catalina.core.StandardServer.start(StandardServer.java:710)
at org.apache.catalina.startup.Catalina.start(Catalina.java:578)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
at java.lang.reflect.Method.invoke(Method.java:597)
at org.apache.catalina.startup.Bootstrap.start(Bootstrap.java:288)
at org.apache.catalina.startup.Bootstrap.main(Bootstrap.java:413)
Caused by: com.sun.faces.config.ConfigurationException: Unable to parse document 'jar:file:/C:/servers/apache-tomcat-6.0.16/webapps/myWebApp/WEB-INF/lib/jsf-impl-1.2.jar!/com/sun/faces/jsf-ri-runtime.xml': This parser does not support specification "null" version "null"
at com.sun.faces.config.ConfigManager$ParseTask.call(ConfigManager.java:409)
at com.sun.faces.config.ConfigManager$ParseTask.call(ConfigManager.java:353)
at java.util.concurrent.FutureTask$Sync.innerRun(FutureTask.java:303)
at java.util.concurrent.FutureTask.run(FutureTask.java:138)
at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:885)
at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:907)
at java.lang.Thread.run(Thread.java:619)
I thought this would have something to do with the xml parser so i added jaxb and jaxp to the application but I still get the same error. Can anyone help? Is there a possibility that a library in the app is overriding jaxb/jaxp?

I had a similar problem on OC4J. For some crazy reason, Oracle still bundles their own XML parser (I say still. It's OC4J 10.1.3 we have in production, so we're just a wee bit behind the curve). At any rate, I had to tell OC4j not to use Oracle's XML parser and just the one bundle with the JRE (1.5). IIRC (and I should know this since I work on Mojarra :), that's caused by an older version of JAXB, so I think you're on the right track. You might check to see if Tomcat 6 bundles JAXB. If it does, you'll need to remove it or update it. If you're on 1.5 or greater, I don't think you need to have that in the app server lib anyway, as the JDK/JRE bundles it.
Hope that helps. :)

JSF 1.2 and JSP 2.1

hi all
i would like to know does JSP 2.1 apart for providing the Unified EL, also does away with the life cycle mixing of JSP and JSF as in previous combination such as jsf 1.1 and JSP .
also would facelets be a better performer???
Rajat

It is tough to say if facelets would be a better performer or not a priori. You would probably have to instrument your application to discover this.
JSPs are compiled into Java classes and so might run faster. OTOH, they likely have a heavier footprint (more memory used to load the classes and the interned strings).
I don't know enough about facelets internals to know for certain, but suppose each facelet has a lighter footprint. Then you probably start with JSPs performing better with facelets catching up as you add more and more pages.
But sometimes these things do not work out the may you might theorize. E.g., few people predicted that Java would be a performer on the server and that in fact the Java application performs better the longer it runs.
Don't take anything I've said here as gospel, I am just speculating.

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

JSF 1.1 and JSF 1.2 source

Hi ,
I am new to JSF ...
I need source code for JSF 1.1 and 1.2 ...
Any pointers would be appreciated..
Thanks
Kurt

Start here: http://javaserverfaces.dev.java.net

JSF 2.0 and Weblogic 10.3.6

Hi,
I am planning to use JSF 2.0 on Weblogic Server 10.3.6.
What implementation of JSF 2.0 is used by weblogic servers ( Mojarra ?)
Is a Reference Implementation like Mojarra, compatible to be used with other component libraries ?
Thanks

Why don't you ask Weblogic questions in the Weblogic forums? https://forums.oracle.com/forums/category.jspa?categoryID=193
If you startup the server with a simple webapp deployed to it you should be able to see in the server log which implementation of JSF is there. A simple text search for "Mojarra" should already tell you if it is used or not. A simple google query for "weblogic 10.3 mojarra" seems to indicate it is in fact Mojarra for both JSF 1.2 and 2.0.

Relevent specifications for JSF 2.0 and JSTL 1.2 specification evaluation.

Hi,
I am studying final draft version of JSF 2.0.
What all other specifications required for JSF 2.0 and JSTL 1.2 specification evaluation with respect to glass fish 3.0.
Please let me know what all other JSRs required to go through.
Thanks,
Ravi

You will want a solid understanding of Servlets.
You may want to use EJBs and EARs; then again, you may not.

Problem with JSF 1.2 and Tomcat 6

Hello guys,
I have here:
Tomcat 6.0.10
JSF 1.2_04_b10_p01
I followed these steps without success:
http://forum.java.sun.com/thread.jspa?threadID=787962
http://forum.java.sun.com/thread.jspa?threadID=5156242
Here what I did:
1) Removed the following line in $TOMCAT_HOME/conf/server.xml
<Listener className="org.apache.catalina.core.AprLifecycleListener" SSLEngine="on" />2) Add the following lines to $TOMCAT_HOME/conf/web.xml
     <context-param>
     <param-name>com.sun.faces.expressionFactory</param-name>
     <param-value>org.apache.el.ExpressionFactoryImpl</param-value>
     </context-param>3) Add the following libs to $TOMCAT_HOME/lib
jsf-api.jar
jsf-impl.jar
jstl-1.2.jar
4) Add the following lines to $MYAPP/WEB-INF/web.xml
     <listener>
          <listener-class>
               com.sun.faces.config.ConfigureListener
          </listener-class>
     </listener>
     <listener>
          <listener-class>
               com.sun.faces.application.WebappLifecycleListener
          </listener-class>
     </listener>And here is "the final product":
INFO: Initializing Sun's JavaServer Faces implementation (1.2_04-b10-p01) for context '/protocolo'
10/04/2007 08:18:47 com.sun.faces.config.ConfigureListener registerELResolverAndListenerWithJsp
SEVERE: Error Instantiating ExpressionFactory
java.lang.ClassCastException: org.apache.el.ExpressionFactoryImpl cannot be cast to javax.el.ExpressionFactory
     at com.sun.faces.config.ConfigureListener.registerELResolverAndListenerWithJsp(ConfigureListener.java:1563)
     at com.sun.faces.config.ConfigureListener.contextInitialized(ConfigureListener.java:419)
     at org.apache.catalina.core.StandardContext.listenerStart(StandardContext.java:3827)
     at org.apache.catalina.core.StandardContext.start(StandardContext.java:4336)
     at org.apache.catalina.core.ContainerBase.addChildInternal(ContainerBase.java:761)
     at org.apache.catalina.core.ContainerBase.addChild(ContainerBase.java:741)
     at org.apache.catalina.core.StandardHost.addChild(StandardHost.java:525)
     at org.apache.catalina.startup.HostConfig.deployWAR(HostConfig.java:825)
     at org.apache.catalina.startup.HostConfig.deployWARs(HostConfig.java:714)
     at org.apache.catalina.startup.HostConfig.deployApps(HostConfig.java:490)What I need to do? Someone can help me?
Thank you.

Thank you for the answer rlubke,
Well this happened because I had compiled the project with the jstl-1.1
The workaround to make jsf 1.2 run on tomcat 6 really works.
But now I have a problem because the JNDI tree in tomcat is read-only ( ro )
and I need to bind a object in the JNDI so an exception happens:
WARNING: Ocorreu um erro inexperado:
javax.naming.NamingException: Context is read only
         at org.apache.naming.NamingContext.checkWritable(NamingContext.java:903)
         at org.apache.naming.NamingContext.bind(NamingContext.java:831)
         at org.apache.naming.NamingContext.bind(NamingContext.java:171)
         at org.apache.naming.NamingContext.bind(NamingContext.java:187)
         at org.apache.naming.SelectorContext.bind(SelectorContext.java:171)
         at javax.naming.InitialContext.bind(InitialContext.java:400)Here is the code:
try{
     Context newContext = new InitialContext();
     newContext.bind( dataSourceWrappedID, wrappedDs );
     newContext.close();
}catch(NameAlreadyBoundException nabe){
     // ok no problem..
}catch(NamingException ne){
     if ( log.isWarnEnabled() ){
          log.warn("Ocorreu um erro inexperado:", ne);
}You know how to make the JNDI tree in tomcat read-write ?
Thank you a ton. :-)

JSF 1.2 and

Similar Messages

Maybe you are looking for