Hi,

I wrote a simple class called SimpleTest and mapped an action called
"simple" in the sitemap.

The exception that I am getting is:
org.apache.avalon.framework.component.ComponentException: UnnamedSelector:
ComponentSelector could not find the component for hint: simple
        at
org.apache.avalon.excalibur.component.DefaultComponentSelector.select(Defaul
tComponentSelector.java:177)
        at org.apache.cocoon.www.sitemap_xmap.process(sitemap_xmap.java:3838)
        at org.apache.cocoon.www.sitemap_xmap.process(sitemap_xmap.java:1344)
        at org.apache.cocoon.sitemap.Handler.process(Handler.java:175)
        at org.apache.cocoon.sitemap.Manager.invoke(Manager.java:94)
        at org.apache.cocoon.Cocoon.process(Cocoon.java:293)
        at org.apache.cocoon.servlet.CocoonServlet.service(CocoonServlet.java:471)
        at javax.servlet.http.HttpServlet.service(HttpServlet.java:853)
        at org.apache.tomcat.core.ServletWrapper.doService(ServletWrapper.java:405)
        at org.apache.tomcat.core.Handler.service(Handler.java:287)
        at org.apache.tomcat.core.ServletWrapper.service(ServletWrapper.java:372)
        at
org.apache.tomcat.core.ContextManager.internalService(ContextManager.java:79
7)
        at org.apache.tomcat.core.ContextManager.service(ContextManager.java:743)
        at
org.apache.tomcat.service.http.HttpConnectionHandler.processConnection(HttpC
onnectionHandler.java:213)
        at
org.apache.tomcat.service.TcpWorkerThread.runIt(PoolTcpEndpoint.java:416)
        at
org.apache.tomcat.util.ThreadPool$ControlRunnable.run(ThreadPool.java:501)
        at java.lang.Thread.run(Thread.java:484)

I modified web.xml to include the absolute path of the web.xml.
I am attaching the cocoon.log, web.xml and sitemap.xmap. I would appreciate
any help or pointers for information.

Thanks,

Dinkar

sitemap.xmap

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

<!--
  This is the web-app configurations that allow Cocoon to work under
  Apache Tomcat. Please, follow the installation section of the
  documentation for more information about installing Cocoon on Tomcat
-->

<!DOCTYPE web-app
    PUBLIC "-//Sun Microsystems, Inc.//DTD Web Application 2.2//EN"
    "http://java.sun.com/j2ee/dtds/web-app_2.2.dtd";>

<web-app>
  <display-name>Cocoon2 Demo</display-name>
  <description>Demo application for Cocoon2</description>
  <servlet>
    <servlet-name>Cocoon2</servlet-name>
    <display-name>Cocoon2</display-name>
    <description>The main Cocoon2 servlet</description>

    <!--
      In cases you're facing class loader problems you can alternatively 
      use the following servlet-class instead of the normal one

      
    <servlet-class>org.apache.cocoon.servlet.CocoonServlet</servlet-class>  
    -->
<servlet-class>org.apache.cocoon.servlet.ParanoidCocoonServlet</servlet-class>

    <!--
      This parameter points to the main configuration file for Cocoon.
      Note that the path is specified in absolute notation but it will be
      resolved relative to the servlets webapp context path
    -->
    <init-param>
      <param-name>configurations</param-name>
      <param-value>/cocoon.xconf</param-value>
    </init-param>

    <!--
      This parameter indicates the log level to use throughout the system

      Available levels are:
        DEBUG:        prints all level of log messages.
        INFO:         prints all level of log messages except DEBUG ones.
        WARN:         prints all level of log messages except DEBUG and INFO ones.
        ERROR:        prints all level of log messages except DEBUG, INFO and WARN ones.
        FATAL-ERROR: prints only log messages of this level
    -->
    <init-param>
      <param-name>log-level</param-name>
      <param-value>DEBUG</param-value>
    </init-param>

    <!--
      This parameter indicates the directory where Cocoon should put the log file.
      Note that this path must be specified as an absolute path into your filesystem
      and it is not rooted at the servlets context path. Also note that the path 
      must end with a file separator character.
      The default location is in the servlets context root at /WEB-INF/logs/.

    <init-param>
      <param-name>log-dir</param-name>
      <param-value>/WEB-INF/logs</param-value>
    </init-param>
    -->

    <!--
      This parameter specifies the name of the log file to use. It will be created in 
      the log-dir mentioned above.
      The default name is "cocoon.log".

    <init-param>
      <param-name>log-name</param-name>
      <param-value>cocoon.log</param-value>
    </init-param>
    -->
  
    <!-- 
      Allow reinstantiating (reloading) of the cocoon instance. If this is
      set to "yes" or "true", a new cocoon instance can be created using
      the request parameter "cocoon-reload".
    -->
    <init-param>
      <param-name>allow-reload</param-name>
      <param-value>yes</param-value>
    </init-param>
  
    <!-- 
      This parameter is used to list classes that should be loaded
      at initialization time of the servlet.
      Usually this classes are JDBC Drivers used
    -->
    <init-param>

      <param-name>load-class</param-name>
      <param-value>
        <!-- For IBM WebSphere: -->
        com.ibm.servlet.classloader.Handler

        <!-- For Database Driver: -->
        org.hsqldb.jdbcDriver
      </param-value>
    </init-param>
      
    <!-- 
      This parameter allows to specify where Cocoon should put files 
      which are uploaded by the upload.xsp sample. The path specified 
      is always relative to the context path of the servlet. 
      The default directory is "image-dir" in the work-directory

    <init-param>
      <param-name>upload-directory</param-name>
      <param-value>/WEB-INF/work/image-dir</param-value>
    </init-param>
    -->
  
    <!-- 
      This parameter allows to specify where Cocoon should put it's
      working files. The path specified is always relative to the 
      context path of the Cocoon servlet. 
      Usually it is obtained from the servlet engine.

    <init-param>
      <param-name>work-directory</param-name>
      <param-value>/WEB-INF/work</param-value>
    </init-param>
    -->
  
    <!-- 
      This parameter allows to specify additional directories or jars 
      which Cocoon should put into it's own classpath.
      Note that you must separate them using the platforms path.separator
      (":" for *nix and ";" for Windows systems). Also not that absolute 
      pathes are take as such but relative pathes are rooted at the context
      root of the Cocoon servlet.
      -->
    <init-param>
      <param-name>extra-classpath</param-name>
      <param-value>;c:\dinkar\cocoon_test</param-value>
    </init-param>
    
  </servlet>

  <servlet-mapping>
    <servlet-name>Cocoon2</servlet-name>
    <url-pattern>/</url-pattern>
  </servlet-mapping>
</web-app>

---------------------------------------------------------------------
Please check that your question has not already been answered in the
FAQ before posting. <http://xml.apache.org/cocoon/faqs.html>

To unsubscribe, e-mail: <[EMAIL PROTECTED]>
For additional commands, e-mail: <[EMAIL PROTECTED]>

Reply via email to