Fixed - Re: XSPProcessor

[Robert Schmid <ro...@fourthgen.com>]

Now that was just embarassing.  Here I was slavishly obeying the 
instructions and didn't even bother to wonder about those extra jar files.

Thanks!


At 10:31 AM 10/20/2000 -0700, you wrote:
>Looks like turbine-pool.jar is not included in the classpath, try adding 
>this in tomcat.bat.
>
>Srinivas
>>----- Original Message -----
>>From: <ma...@Barra.COM>Padma Ramaraju
>>To: <mailto:'cocoon-users@xml.apache.org'>'cocoon-users@xml.apache.org'
>>Sent: Friday, October 20, 2000 9:49 AM
>>Subject: XSPProcessor
>>
>>Hi All!
>>
>>I am sure some one have had this problem before.  I started to explore 
>>Cocoon just a few days back.  I have TomCat version 3.1 and Cocoon 
>>version 1.8.  I am trying to open an xml file in IE5.0 and I get the 
>>following error:
>>
>>***************************************************
>>Publishing Engine could not be initialized. java.lang.RuntimeException: 
>>Error creating org.apache.cocoon.processor.xsp.XSPProcessor: make sure 
>>the needed classes can be found in the classpath 
>>(org/apache/turbine/services/resources/TurbineResourceService)  at 
>>org.apache.cocoon.framework.Manager.create(Manager.java:114)         at 
>>org.apache.cocoon.framework.Router.init(Router.java, Compiled Code)  at 
>>org.apache.cocoon.framework.Manager.create(Manager.java:101)         at 
>>org.apache.cocoon.Engine.(Engine.java:171)   at 
>>org.apache.cocoon.Engine.getInstance(Engine.java:218)        at 
>>org.apache.cocoon.Cocoon.init(Cocoon.java:141)       at 
>>org.apache.tomcat.core.ServletWrapper.initServlet(ServletWrapper.java, 
>>Compiled Code)        at 
>>org.apache.tomcat.core.ServletWrapper.handleRequest(ServletWrapper.java, 
>>Compiled Code)      at 
>>org.apache.tomcat.core.ContextManager.service(ContextManager.java:559) 
>>at 
>>org.apache.tomcat.service.http.HttpConnectionHandler.processConnection(HttpConnectionHandler.java, 
>>Compiled Code)    at 
>>org.apache.tomcat.service.TcpConnectionThread.run(SimpleTcpEndpoint.java, 
>>Compiled Code)     at java.lang.Thread.run(Thread.java, Compiled Code)
>>Warning: this page has been dynamically generated.
>>
>>Copyright (c) 1999-2000 The Apache XML Project 
>><<http://xml.apache.org>http://xml.apache.org>.
>>All rights reserved.
>>
>>****************************************
>>
>>Here is my xml file:
>>
>><?xml version="1.0" encoding="ISO-8859-1" ?>
>>- <web-app>
>>- <servlet>
>><servlet-name>snoop</servlet-name>
>><servlet-class>SnoopServlet</servlet-class>
>>- <!--
>>         <init-param>
>>             <param-name>foo</param-name>
>>             <param-value>bar</param-value>
>>         </init-param>
>>-->
>></servlet>
>>- <servlet>
>><servlet-name>servletToJsp</servlet-name>
>><servlet-class>servletToJsp</servlet-class>
>></servlet>
>>- <servlet-mapping>
>><servlet-name>snoop</servlet-name>
>><url-pattern>/snoop</url-pattern>
>></servlet-mapping>
>>- <servlet-mapping>
>><servlet-name>snoop</servlet-name>
>><url-pattern>*.snp</url-pattern>
>></servlet-mapping>
>>- <servlet-mapping>
>><servlet-name>servletToJsp</servlet-name>
>><url-pattern>/servletToJsp</url-pattern>
>></servlet-mapping>
>>- <taglib>
>><taglib-uri><http://java.apache.org/tomcat/examples-taglib>http://java.apache.org/tomcat/examples-taglib</taglib-uri> 
>>
>><taglib-location>/WEB-INF/jsp/example-taglib.tld</taglib-location>
>></taglib>
>>- <security-constraint>
>>- <web-resource-collection>
>><web-resource-name>Protected Area</web-resource-name>
>>- <!--
>>  Define the context-relative URL(s) to be protected
>>-->
>><url-pattern>/jsp/security/protected/*</url-pattern>
>>- <!--
>>  If you list http methods, only those methods are protected
>>-->
>><http-method>DELETE</http-method>
>><http-method>GET</http-method>
>><http-method>POST</http-method>
>><http-method>PUT</http-method>
>></web-resource-collection>
>>- <auth-constraint>
>>- <!--
>>  Anyone with one of the listed roles may access this area
>>-->
>><role-name>tomcat</role-name>
>><role-name>role1</role-name>
>></auth-constraint>
>></security-constraint>
>>- <!--
>>  Default login configuration uses BASIC authentication
>>-->
>>- <login-config>
>><auth-method>BASIC</auth-method>
>><realm-name>Example Basic Authentication Area</realm-name>
>></login-config>
>>- <!--
>>  If you want to experiment with form-based logins, comment
>>          out the <login-config> element above and replace it with
>>          this one.  Note that we are currently using a nonstandard
>>          authentication method, because the code to support form
>>          based login is incomplete and only lightly tested.
>>-->
>>- <!--
>>     <login-config>
>>       <auth-method>EXPERIMENTAL_FORM</auth-method>
>>       <realm-name>Example Form-Based Authentication Area</realm-name>
>>       <form-login-config>
>>         <form-login-page>/jsp/security/login/login.jsp</form-login-page>
>>         <form-error-page>/jsp/security/login/error.jsp</form-error-page>
>>       </form-login-config>
>>     </login-config>
>>
>>-->
>></web-app>
>>I have added "cocoon.jar" in the classpath in tomcat.bat file.  Any help 
>>is appreciated.
>>
>>thanks,
>>Padma.