In case AutoConfig is that feature that Tomcat suggests obj.conf entries : this one 
finally got generated in /conf/auto/obj.conf and it is good for handing whole 
directories over and hiding WEB-INF, but how can it help in this special problem?


-----Urspr�ngliche Nachricht-----
Von: Bill Barker [mailto:[EMAIL PROTECTED]
Gesendet am: Montag, 30. Juni 2003 11:52
An: [EMAIL PROTECTED]
Betreff: Re: Content Management in integrated iPlanet/Tomcat

Have you tried using the AutoConfig?

"Marquardt Angela" <[EMAIL PROTECTED]> wrote in message
news:[EMAIL PROTECTED]
> Hi,
>
> I have a problem mapping JSP content from iPlanet to Tomcat, due to
"historical" content distribution in different directories. It is not
possible to generate war files and deploy those.
>
> This is my setup:
> Tomcat is installed in /opt/Tomcat and looks for content relative to the
install dir.
> With a context description it is possible to map the webapps directory to
a different path, f.e. webapps_addon, but still this has to be under the
install dir.
>
> Now, there is content in a /content directory as well as in /content1.
> JSP Files, which have to be processed by the Tomcat Engine, are located in
both, and JSPs in f.e. /content/tools use files in /content/images or
/content/dhtml.
>
> 1. A link from /opt/Tomcat/webapps/tools to /content/tools did not work
and generates 404 error.
> 2. Copying /content/tools, /content/images, /content/dhtml ...  to
/opt/Tomcat/webapps hands over more content than possible to Tomcat Servlet
Engine.
> 3. Installing Tomcat in /content would prevent JSPs in /content1 from
being executed.
>
> Which possibilities are there to configure that? Any hint will be
appreciated.
>
> Cheers, Angela




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

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

Reply via email to