Thanks for the response.

I have a listener entry like this one in the web.xml file:

<listener>
        
<listener-class>org.apache.myfaces.webapp.StartupServletContextListener</listener-class>
 </listener>

//////////// Below is a dump of the web.xml file ///////


    xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance";
    xsi:schemaLocation="http://java.sun.com/xml/ns/j2ee 
http://java.sun.com/xml/ns/j2ee/web-app_2_4.xsd";
    version="2.4">
    <display-name>NCC Copyright Notification</display-name>
    <context-param>
        <param-name>
            org.apache.myfaces.CHECK_EXTENSIONS_FILTER
        </param-name>
        <param-value>true</param-value>
    </context-param>
    <context-param>
        <param-name>javax.faces.CONFIG_FILES</param-name>
        <param-value>
            /WEB-INF/faces-config.xml
        </param-value>
    </context-param>

    <context-param>
        <param-name>javax.faces.STATE_SAVING_METHOD</param-name>
        <param-value>client</param-value>
        <!--<description>State saving method: "client" or "server" (= default) 
See JSF Specification 2.5.2 </
description>-->
    </context-param>

    <context-param>
        <param-name>org.apache.myfaces.ALLOW_JAVASCRIPT</param-name>
        <param-value>true</param-value>
       <!-- <description>
            This parameter tells MyFaces if javascript code should be allowed 
in the
            rendered HTML output.
            If javascript is allowed, command_link anchors will have javascript 
code
            that submits the corresponding form.
            If javascript is not allowed, the state saving info and nested 
parameters
            will be added as url parameters.
            Default: "true"
        </description>-->
    </context-param>

    <context-param>
        <param-name>org.apache.myfaces.PRETTY_HTML</param-name>
        <param-value>true</param-value>
        <!--<description>
            If true, rendered HTML code will be formatted, so that it is "human 
readable".
            i.e. additional line separators and whitespace will be written, 
that do not
            influence the HTML code.
            Default: "true"
        </description>-->
    </context-param>

    <context-param>
        <param-name>org.apache.myfaces.DETECT_JAVASCRIPT</param-name>
        <param-value>false</param-value>
    </context-param>

    <context-param>
        <param-name>org.apache.myfaces.AUTO_SCROLL</param-name>
        <param-value>true</param-value>
        <!--<description>
            If true, a javascript function will be rendered that is able to 
restore the
            former vertical scroll on every request. Convenient feature if you 
have pages
            with long lists and you do not want the browser page to always jump 
to the top
            if you trigger a link or button action that stays on the same page.
            Default: "false"
        </description>-->
    </context-param>

    <!-- Extensions Filter -->
    <filter>
        <filter-name>MyFacesExtensionsFilter</filter-name>
        
<filter-class>org.apache.myfaces.webapp.filter.ExtensionsFilter</filter-class>
        <init-param>
            <param-name>maxFileSize</param-name>
            <param-value>20m</param-value>
            <!--<description>Set the size limit for uploaded files. Format: 10 
- 10 bytes, 10k - 10 KB,10m -
10 MB,1g - 1 GB</description>-->
        </init-param>
    </filter>

    <!-- extension mapping for adding <script/>, <link/>, and other resource 
tags to JSF-pages  -->
    <filter-mapping>
        <filter-name>MyFacesExtensionsFilter</filter-name>
        <!-- servlet-name must match the name of your 
javax.faces.webapp.FacesServlet entry -->
        <servlet-name>Faces Servlet</servlet-name>
    </filter-mapping>

    <!-- extension mapping for serving page-independent resources (javascript, 
stylesheets, images, etc.)  --
>
    <filter-mapping>
        <filter-name>MyFacesExtensionsFilter</filter-name>
        <url-pattern>/faces/myFacesExtensionResource/*</url-pattern>
    </filter-mapping>
    <!-- Listener, that does all the startup work (configuration, init). -->
    <listener>
        
<listener-class>org.apache.myfaces.webapp.StartupServletContextListener</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-mapping>
        <servlet-name>Faces Servlet</servlet-name>
        <url-pattern>*.faces</url-pattern>
    </servlet-mapping>
    <!-- Welcome files -->
    <welcome-file-list>
        <welcome-file>index.jsp</welcome-file>
        <welcome-file>index.faces</welcome-file>
    </welcome-file-list>
</web-app>



----- Original Message ----
From: "Nebinger, David" <[EMAIL PROTECTED]>
To: MyFaces Discussion <[email protected]>
Sent: Thursday, May 3, 2007 2:51:33 PM
Subject: RE: SEVERE: Exception ... class 
org.apache.myfaces.webapp.StartupServletContextListener

> I am getting the following error when I attempt to deploy my 
> application in tomcat 5.5.15
> 
> SEVERE: Exception sending context initialized event to 
> listener instance of class 
> org.apache.myfaces.webapp.StartupServletContextListener
> 
> I see the above error in /var/log/tomcat5/catalina.out

Do you have the listener defined in your web.xml file?




__________________________________________________
Do You Yahoo!?
Tired of spam?  Yahoo! Mail has the best spam protection around 
http://mail.yahoo.com 

Reply via email to