|
|
Re: Deploying to the root context... [message #171030 is a reply to message #170416] |
Sat, 10 June 2006 17:46 |
Eclipse User |
|
|
|
Originally posted by: tobias.domain.hidden.com
Hi Larry,
I found your reply to this message and thought you we're giving us a
workaround for bug 125364. After reading up on your responses in
bugzilla I also found this statement from you "Disabling the auto
serving of webapps should avoid the extra version of the webapp being
served based on the project name.", this was on bug 137628. However, I
can't get it to work. Using the latest RC of the eclipse platform and
the latest WTP RC i've configured my app to run as the default app and
set @autoDeploy="false" on /Server/Service/Engine/Host in server.xml. Is
there something more I need to do or am I mistaken altogether and there
is no quick-fix for the 'two-copies-of-webapp' problem?
Larry Isaacs wrote:
> Disabling the auto-deployment feature in the server.xml found under the
> Servers project in your workspace should avoid the multiple loading
> problem.
>
> Cheers,
> Larry
>
> Nathan Wilhelmi wrote:
>> Hello - We have several applications that hard coded to only run in
>> the root context. They will not be fixed so I am trying to find some
>> work arounds. The problem I have been having is that the web
>> application gets loaded at least twice when deployed through eclipse.
>> I have found that if you manually edit the config files you can set
>> the context root to an empty string, and it gets deployed at the root
>> context, however with the multiple loading problems. The GUI will not
>> let you do this. Is there anyway in WTP to deploy to the root context
>> that is supported and not cause the application to be loaded multiple
>> times?
>>
>> Thanks!
>>
>> -Nate
|
|
|
|
Powered by
FUDForum. Page generated in 0.05133 seconds