Hi, thx for ur answer
I make the quickstart example work by adding .jar in
WEB-INF/lib directory of my .war but I'd like to put
Cactus jars in my container classpath so that Cactus
will load them using the container Context class
loader, but i don't know how to make it !!!
My app's name is test (test.war)
I don't have a cactus.properties ? What is that ?
I don't know where I have to put the .jar in jboss and
wich web.xml I have to modify, conf/web.xml or
deploy/jboss-tomcat*/web.xml
Here is my conf/web.xml :
<?xml version="1.0" encoding="ISO-8859-1"?>
<!DOCTYPE web-app
PUBLIC "-//Sun Microsystems, Inc.//DTD Web
Application 2.3//EN"
"http://java.sun.com/dtd/web-app_2_3.dtd";>
<web-app>
<!-- Debut ajout SF -->
<filter>
<filter-name>FilterRedirector</filter-name>
<filter-class>org.apache.cactus.server.FilterTestRedirector</filter-class>
</filter>
<filter-mapping>
<filter-name>FilterRedirector</filter-name>
<url-pattern>/FilterRedirector</url-pattern>
</filter-mapping>
<servlet>
<servlet-name>ServletRedirector</servlet-name>
<servlet-class>org.apache.cactus.server.ServletTestRedirector</servlet-class>
<init-param>
<param-name>param1</param-name>
<param-value>value1 used for
testing</param-value>
</init-param>
</servlet>
<servlet>
<servlet-name>JspRedirector</servlet-name>
<jsp-file>/jspRedirector.jsp</jsp-file>
</servlet>
<servlet>
<servlet-name>ServletTestRunner</servlet-name>
<servlet-class>org.apache.cactus.server.runner.ServletTestRunner</servlet-class>
</servlet>
<!-- Fin ajout SF -->
<!-- ======================== Introduction
============================== -->
<!-- This document defines default values for *all*
web applications -->
<!-- loaded into this instance of Tomcat. As each
application is -->
<!-- deployed, this file is processed, followed by
the -->
<!-- "/WEB-INF/web.xml" deployment descriptor from
your own -->
<!-- applications.
-->
<!--
-->
<!-- WARNING: Do not configure application-specific
resources here! -->
<!-- They should go in the "/WEB-INF/web.xml" file
in your application. -->
<!-- ================== Built In Servlet Definitions
==================== -->
<!-- The default servlet for all web applications,
that serves static -->
<!-- resources. It processes all requests that are
not mapped to other -->
<!-- servlets with servlet mappings (defined either
here or in your own -->
<!-- web.xml file. This servlet supports the
following initialization -->
<!-- parameters (default values are in square
brackets): -->
<!--
-->
<!-- debug Debugging detail level
for messages logged -->
<!-- by this servlet. [0]
-->
<!--
-->
<!-- input Input buffer size (in
bytes) when reading -->
<!-- resources to be served.
[2048] -->
<!--
-->
<!-- listings Should directory listings
be produced if there -->
<!-- is no welcome file in
this directory? [true] -->
<!--
-->
<!-- output Output buffer size (in
bytes) when writing -->
<!-- resources to be served.
[2048] -->
<!--
-->
<!-- readonly Is this context "read
only", so HTTP -->
<!-- commands like PUT and
DELETE are -->
<!-- rejected? [true]
-->
<servlet>
<servlet-name>default</servlet-name>
<servlet-class>
org.apache.catalina.servlets.DefaultServlet
</servlet-class>
<init-param>
<param-name>debug</param-name>
<param-value>0</param-value>
</init-param>
<init-param>
<param-name>listings</param-name>
<param-value>true</param-value>
</init-param>
<load-on-startup>1</load-on-startup>
</servlet>
<!-- The "invoker" servlet, which executes anonymous
servlet classes -->
<!-- that have not been defined in a web.xml file.
Traditionally, this -->
<!-- servlet is mapped to URL pattern "/servlet/*",
but you can map it -->
<!-- to other patterns as well. The extra path info
portion of such a -->
<!-- request must be the fully qualified class name
of a Java class that -->
<!-- implements Servlet (or extends HttpServlet), or
the servlet name -->
<!-- of an existing servlet definition. This
servlet supports the -->
<!-- following initialization parameters (default
values are in square -->
<!-- brackets):
-->
<!--
-->
<!-- debug Debugging detail level
for messages logged -->
<!-- by this servlet. [0]
-->
<servlet>
<servlet-name>invoker</servlet-name>
<servlet-class>
org.apache.catalina.servlets.InvokerServlet
</servlet-class>
<init-param>
<param-name>debug</param-name>
<param-value>0</param-value>
</init-param>
<load-on-startup>2</load-on-startup>
</servlet>
<!-- The JSP page compiler and execution servlet,
which is the mechanism -->
<!-- used by Tomcat to support JSP pages.
Traditionally, this servlet -->
<!-- is mapped to URL patterh "*.jsp". This servlet
supports the -->
<!-- following initialization parameters (default
values are in square -->
<!-- brackets):
-->
<!--
-->
<!-- checkInterval If development is false
and reloading is true, -->
<!-- background compiles are
enabled. checkInterval -->
<!-- is the time in seconds
between checks to see -->
<!-- if a JSP page needs to be
recompiled. [300] -->
<!--
-->
<!-- compiler Which compiler Ant should
use to compile JSP -->
<!-- pages. See the Ant
documenation for more -->
<!-- information. [javac]
-->
<!--
-->
<!-- classdebuginfo Should the class file be
compiled with -->
<!-- debugging information?
[true] -->
<!--
-->
<!-- classpath What class path should I
use while compiling -->
<!-- generated servlets?
[Created dynamically -->
<!-- based on the current web
application] -->
<!--
-->
<!-- development Is Jasper used in
development mode (will check -->
<!-- for JSP modification on
every access)? [true] -->
<!--
-->
<!-- enablePooling Determines whether tag
handler pooling is -->
<!-- enabled [true]
-->
<!--
-->
<!-- ieClassId The class-id value to be
sent to Internet -->
<!-- Explorer when using
<jsp:plugin> tags. -->
<!--
[clsid:8AD9C840-044E-11D1-B3E9-00805F499D93] -->
<!--
-->
<!-- fork Tell Ant to fork compiles
of JSP pages so that -->
<!-- a separate JVM is used
for JSP page compiles -->
<!-- from the one Tomcat is
running in. [true] -->
<!--
-->
<!-- javaEncoding Java file encoding to use
for generating java -->
<!-- source files. [UTF8]
-->
<!--
-->
<!-- keepgenerated Should we keep the
generated Java source code -->
<!-- for each page instead of
deleting it? [true] -->
<!--
-->
<!-- largefile Should we store the
static content of JSP -->
<!-- pages in external data
files, to reduce the -->
<!-- size of the generated
servlets? [false] -->
<!--
-->
<!-- logVerbosityLevel The level of detailed
messages to be produced -->
<!-- by this servlet.
Increasing levels cause the -->
<!-- generation of more
messages. Valid values are -->
<!-- FATAL, ERROR, WARNING,
INFORMATION, and DEBUG. -->
<!-- [WARNING]
-->
<!--
-->
<!-- mappedfile Should we generate static
content with one -->
<!-- print statement per input
line, to ease -->
<!-- debugging? [false]
-->
<!--
-->
<!-- reloading Should Jasper check for
modified JSPs? [true] -->
<!--
-->
<!-- scratchdir What scratch directory
should we use when -->
<!-- compiling JSP pages?
[default work directory -->
<!-- for the current web
application] -->
<!--
-->
<!-- If you wish to use Jikes to compile JSP pages:
-->
<!-- Set the init parameter "compiler" to "jikes".
Define -->
<!-- the property "-Dbuild.compiler.emacs=true"
when starting Tomcat -->
<!-- by adding the above to your CATALINA_OPTS
environment variable. -->
<!-- If you get an error reporting that jikes
can't use UTF8 encoding, -->
<!-- try setting the init parameter "javaEncoding"
to "ISO-8859-1". -->
<servlet>
<servlet-name>jsp</servlet-name>
<servlet-class>org.apache.jasper.servlet.JspServlet</servlet-class>
<init-param>
<param-name>logVerbosityLevel</param-name>
<param-value>WARNING</param-value>
</init-param>
<load-on-startup>3</load-on-startup>
</servlet>
<!-- Server Side Includes processing servlet, which
processes SSI -->
<!-- directives in HTML pages consistent with
similar support in web -->
<!-- servers like Apache. Traditionally, this
servlet is mapped to -->
<!-- URL pattern "*.shtml". This servlet supports
the following -->
<!-- initialization parameters (default values are
in square brackets): -->
<!--
-->
<!-- buffered Should output from this
servlet be buffered? -->
<!-- (0=false, 1=true) [0]
-->
<!--
-->
<!-- debug Debugging detail level
for messages logged -->
<!-- by this servlet. [0]
-->
<!--
-->
<!-- expires The number of seconds
before a page with SSI -->
<!-- directives will expire.
[No default] -->
<!--
-->
<!-- isVirtualWebappRelative
-->
<!-- Should "virtual" paths be
interpreted as -->
<!-- relative to the context
root, instead of -->
<!-- the server root?
(0=false, 1=true) [0] -->
<!--
-->
<!--
-->
<!-- IMPORTANT: To use the SSI servlet, you also
need to rename the -->
<!--
$CATALINA_HOME/server/lib/servlets-ssi.renametojar
file -->
<!-- to
$CATALINA_HOME/server/lib/servlets-ssi.jar
-->
<!--
<servlet>
<servlet-name>ssi</servlet-name>
<servlet-class>
org.apache.catalina.ssi.SSIServlet
</servlet-class>
<init-param>
<param-name>buffered</param-name>
<param-value>1</param-value>
</init-param>
<init-param>
<param-name>debug</param-name>
<param-value>0</param-value>
</init-param>
<init-param>
<param-name>expires</param-name>
<param-value>666</param-value>
</init-param>
<init-param>
<param-name>isVirtualWebappRelative</param-name>
<param-value>0</param-value>
</init-param>
<load-on-startup>4</load-on-startup>
</servlet>
-->
<!-- Common Gateway Includes (CGI) processing
servlet, which supports -->
<!-- execution of external applications that conform
to the CGI spec -->
<!-- requirements. Typically, this servlet is
mapped to the URL pattern -->
<!-- "/cgi-bin/*", which means that any CGI
applications that are -->
<!-- executed must be present within the web
application. This servlet -->
<!-- supports the following initialization
parameters (default values -->
<!-- are in square brackets):
-->
<!--
-->
<!-- cgiPathPrefix The CGI search path will
start at -->
<!-- webAppRootDir +
File.separator + this prefix. -->
<!-- [WEB-INF/cgi]
-->
<!--
-->
<!-- clientInputTimeout The time (in
milliseconds) to wait for input -->
<!-- from the browser before
assuming that there -->
<!-- is none. [100]
-->
<!--
-->
<!-- debug Debugging detail level
for messages logged -->
<!-- by this servlet. [0]
-->
<!--
-->
<!-- IMPORTANT: To use the CGI servlet, you also
need to rename the -->
<!--
$CATALINA_HOME/server/lib/servlets-cgi.renametojar
file -->
<!-- to
$CATALINA_HOME/server/lib/servlets-cgi.jar
-->
<!--
<servlet>
<servlet-name>cgi</servlet-name>
<servlet-class>org.apache.catalina.servlets.CGIServlet</servlet-class>
<init-param>
<param-name>clientInputTimeout</param-name>
<param-value>100</param-value>
</init-param>
<init-param>
<param-name>debug</param-name>
<param-value>6</param-value>
</init-param>
<init-param>
<param-name>cgiPathPrefix</param-name>
<param-value>WEB-INF/cgi</param-value>
</init-param>
<load-on-startup>5</load-on-startup>
</servlet>
-->
<!-- Debut ajout SFRE -->
<servlet-mapping>
<servlet-name>ServletRedirector</servlet-name>
<url-pattern>/ServletRedirector</url-pattern>
</servlet-mapping>
<servlet-mapping>
<servlet-name>JspRedirector</servlet-name>
<url-pattern>/JspRedirector</url-pattern>
</servlet-mapping>
<servlet-mapping>
<servlet-name>ServletTestRunner</servlet-name>
<url-pattern>/ServletTestRunner</url-pattern>
</servlet-mapping>
<!-- Debut ajout SFRE -->
<!-- ================ Built In Servlet Mappings
========================= -->
<!-- The servlet mappings for the built in servlets
defined above. Note -->
<!-- that, by default, the CGI and SSI servlets are
*not* mapped. You -->
<!-- must uncomment these mappings (or add them to
your application's own -->
<!-- web.xml deployment descriptor) to enable these
services -->
<!-- The mapping for the default servlet -->
<servlet-mapping>
<servlet-name>default</servlet-name>
<url-pattern>/</url-pattern>
</servlet-mapping>
<!-- The mapping for the invoker servlet -->
<!--
<servlet-mapping>
<servlet-name>invoker</servlet-name>
<url-pattern>/servlet/*</url-pattern>
</servlet-mapping>
-->
<!-- The mapping for the JSP servlet -->
<servlet-mapping>
<servlet-name>jsp</servlet-name>
<url-pattern>*.jsp</url-pattern>
</servlet-mapping>
<!-- The mapping for the SSI servlet -->
<!--
<servlet-mapping>
<servlet-name>ssi</servlet-name>
<url-pattern>*.shtml</url-pattern>
</servlet-mapping>
-->
<!-- The mapping for the CGI Gateway servlet -->
<!--
<servlet-mapping>
<servlet-name>cgi</servlet-name>
<url-pattern>/cgi-bin/*</url-pattern>
</servlet-mapping>
-->
<!-- ==================== Default Session
Configuration ================= -->
<!-- You can set the default session timeout (in
minutes) for all newly -->
<!-- created sessions by modifying the value below.
-->
<session-config>
<session-timeout>30</session-timeout>
</session-config>
<!-- ===================== Default MIME Type
Mappings =================== -->
<!-- When serving static resources, Tomcat will
automatically generate -->
<!-- a "Content-Type" header based on the resource's
filename extension, -->
<!-- based on these mappings. Additional mappings
can be added here (to -->
<!-- apply to all web applications), or in your own
application's web.xml -->
<!-- deployment descriptor.
-->
--- Magnus Mickelsson <[EMAIL PROTECTED]> a
�crit : > Post your cactus.properties and web.xml,
please...
> And what is your app's
> name? (test.war?)
> Also, make sure you have the needed Cactus JARs in
> your Webapp's classpath
> (WEB-INF/lib/ or something..)
>
> /M
>
> > -----Ursprungligt meddelande-----
> > Fr�n: aze N [mailto:[EMAIL PROTECTED]
> > Skickat: den 28 november 2003 14:28
> > Till: [EMAIL PROTECTED]
> > �mne: Cactus & JBoss 3.2.2
> >
> >
> > Hi all,
> >
> > I'm new to Cactus, and I read the doc online, but
> I
> > still have many troubles.
> > I was able to run the quickstart tutorial under
> > Tomcat, but I tried to do the same with JBoss and
> it
> > does not work :-(
> > JBoss throws a mapping configuration error for the
> URI
> > test/ServletTestRunner !!! I think I have a
> problem
> > with my configuration files, but since I'm really
> new
> > to Cactus it's pretty tough to find the problem
> !!!
> > Even after having read the online docs...
> >
> > However, I'm able to run the ejb sample using Ant.
> But
> > I get an error when the server is already started.
> > JBoss throws almost the same error : mapping
> > configuration error for the URI
> > cactus-test/ServletTestRunner
> >
> > I'm lost :-(
> >
> > What have I to change ??? My web.xml file seems to
> be
> > ok.
> >
> > Thx for ur help
>
> ---
> Outgoing mail is certified Virus Free.
> Checked by AVG anti-virus system
> (http://www.grisoft.com).
> Version: 6.0.545 / Virus Database: 339 - Release
> Date: 2003-11-27
>
>
>
---------------------------------------------------------------------
> To unsubscribe, e-mail:
> [EMAIL PROTECTED]
> For additional commands, e-mail:
> [EMAIL PROTECTED]
>
___________________________________________________________
Do You Yahoo!? -- Une adresse @yahoo.fr gratuite et en fran�ais !
Yahoo! Mail : http://fr.mail.yahoo.com
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
