Hi Alex,
I'll check this - but what I said is the syntax used in 3.2 should still
work ( i.e. <RequestInterceptor name="class.name" ... /> ). It is still
used ( more as a sample ) for the connectors.
That doesn't mean the same configuration will work - some of the modules
were rewritten ( authentication, reloading, session - all have been
substantially improven and modularized ), the distinction between
"request" and "context" module has been removed ( and replaced with code
that detects the exact hooks implemented by each module - eliminating
empty calls ), etc.
The logging is now implemented as a "regular" module instead of special
case in the core.
That means you can use the _syntax_ of 3.2, but not the same config
file. You'll need a special server.xml, based on the one in tomcat3.3 if
you want this to work.
Costin
On Thu, 28 Jun 2001, Alex Fernández wrote:
> start_tomcat_32:
> [java] ERROR reading
> E:\proyectos\cactus1.1\sample\out\test\tomcat32\conf\server.xml
> [java] At Line 5 /Server/Logger/ name=tc_log
> [java]
> [java] Java Result: 1
>
> Probably, I'm doing something terribly wrong -- since Costin states
> above that it should work with the -config option.
>
> <ad>Cactus is Jakarta's J2EE test framework; try it out, it's great
> folks!
> http://jakarta.apache.org/commons/cactus/</ad>
>
> Un saludo,
>
> Alex.
>
> > > If this is not possible, perhaps I should add a new .xml file to the
> > > /conf directory and make it run with it? Can Tomcat 3.3 use webapps that
> > > are not inside /webapp?
> >
> > Sure. Just create a new conf/apps-myApp.xml ( using the apps-example.xml
> > as template ), pointing to the dir.
> >
> > It can also autoload all the apps from a different directory - in
> > server.xml you can add a new <AutoWebApp dir="/mywebapp" host="DEFAULT" />
> > You can specify a different virtual host, of course, or set it to
> > use the first level of subdirs as virtual host that will be added
> > automatically and the second for cotnext names in that host.
> >
> > You'll also need to add an <AutoDeploy> if you want .war files expanded
> > ( the current config defaults to the previous behavior, .war files
> > expanded in the same dir - but you can keep them separated ).
> >
> > Speaking of that, you can also try the auto-reload feature when changing
> > the .war file ( which should be re-deployed and the app reloaded ).
> >
> > Costin
>
