I would remove the original WebAppA's work
(%TOMCAT_HOME%\work\yourWebAppA)directory to be sure you are not
picking-up anything from there. Do this before you restart Tomcat after
you have done your directory renames.
--- Wolfgang Egger <[EMAIL PROTECTED]> wrote:
> Servus Wyn,
>
> first thanx for your answer.
>
> > -----Original Message-----
> > I'm sure the problem is with the URL used to access the servlet of
> > WebAppB.
>
> I don't think so, because of the following behaviour:
>
> Our WebServerDirStructure looks like this
>
> /websites/WebAppA
> /websites/WebAppA/WEB-INF
> /websites/WebAppA/WEB-INF/classes
> ...
> /websites/WebAppB
> /websites/WebAppB/WEB-INF
> /websites/WebAppB/WEB-INF/classes
> ...
>
> as written in my first mail the whole site WebAppA is working as
> expected,
> the WebAppB only shows Error 404
> If I remove /websites/WebAppA
>
> and rename /websites/WebAppB with /websites/WebAppA,
> the whole WebAppB is working (with the URR bla/WebAppA/fasel)
>
> Because of this I assume, that something in the configuration of
> tomcat
> doesn't like WebAppB.
> I have done a grep "WebAppA tomcat/conf/*" and a "grep WebAppB
> tomcat/conf/*".
> The result is, that all entries for WebAppA are the same as the
> entries for
> WebAppB. Near the same, because the string WebAppA is replaced by
> WebAppB in
> each entry.
>
> Are there any other locations apart from tomcat/conf, where I have to
> do
> some configuration respectively WebAppB.
>
> Greetings from Berlin
>
> Wolfgang
>
=====
Wyn Easton
[EMAIL PROTECTED]
__________________________________________________
Do You Yahoo!?
Yahoo! Messenger - Talk while you surf! It's FREE.
http://im.yahoo.com/
