ansaurus

Question

How to run my JSF 1.1 application on WAS 6.0

Answer 1

+1 A:

I think WAS has another JSF jar called ws-jsf.jar. Remove it too and try

victor hugo 2009-05-25 23:09:54

Thanks, that surely did it.Along with that, It should be setting to be run as Application, not As module, and to remove the common-loggin1.1 and replace it with common-loggin-adapters1.1

agawish 2009-05-26 12:26:13

Answer 2

A:

 at com.icesoft.faces.webapp.xmlhttp.PersistentFacesServlet.init(Unknown Source)

This servlet is failing to initialize. It might be an idea to go to icesoft.com and find out what it does and why it is failing rather than just deleting files from your app server.

It might be easier to diagnose the problem if you give more details about the technology stack you are using (including the JSF implementation you are deploying with the app).

I made my web module class Loader mode to : Parent Last

This is the correct thing to do. By doing this, your application will use its own JSF implementation instead of the older version in the container. I did not delete any files.

Here the structure of a simple JSF 1.1 application I deployed to WAS 6.0. I used the MyFaces library version 1.1.6.

test.jsp
WEB-INF/faces-config.xml
WEB-INF/web.xml
WEB-INF/lib/commons-beanutils-1.7.0.jar
WEB-INF/lib/commons-el-1.0.jar
WEB-INF/lib/jstl-1.1.0.jar
WEB-INF/lib/commons-collections-3.1.jar
WEB-INF/lib/commons-lang-2.1.jar
WEB-INF/lib/myfaces-api-1.1.6.jar
WEB-INF/lib/commons-digester-1.8.jar
WEB-INF/lib/commons-logging-1.1.1.jar
WEB-INF/lib/myfaces-impl-1.1.6.jar

faces-config.xml doctype:

<!DOCTYPE faces-config PUBLIC
  "-//Sun Microsystems, Inc.//DTD JavaServer Faces Config 1.1//EN"
  "http://java.sun.com/dtd/web-facesconfig_1_1.dtd"&gt;

web.xml:

<?xml version="1.0" encoding="UTF-8"?>
<web-app id="WebApp_ID" 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"&gt;
    <display-name>jsf11</display-name>
    <context-param>
     <param-name>javax.faces.STATE_SAVING_METHOD</param-name>
     <param-value>server</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>
    <servlet-mapping>
     <servlet-name>Faces Servlet</servlet-name>
     <url-pattern>*.faces</url-pattern>
    </servlet-mapping>
</web-app>

McDowell 2009-05-26 12:26:05

Although the class loader is Parent Last, the Websphere JSF implementation the "ws-jsf.jar" still running effectively, the problem is solved after removing this file.I'll provide the steps for what made it successful in the next following days

agawish 2009-05-27 02:19:50

I don't doubt that this solved your problem, and it might be fine if no one else uses the server, but it would not be a solution I would be happy with - it prevents other applications running with the supplied implementation. The JSF bootstrapping process should ignore the container implementation if you configure the classloading correctly and I would want to know the root cause of the NPE in the 3rd party library. Links to detailed info on why deleting the JARs works would be helpful.

McDowell 2009-05-27 09:45:18

ansaurus

tags:

views:

answers:

How to run my JSF 1.1 application on WAS 6.0

related questions