|
|
|
|
|
|
Re: Context Root ignored? [message #540332 is a reply to message #540324] |
Tue, 15 June 2010 12:54   |
Eclipse User |
|
|
|
On 6/15/2010 12:02 PM, Stephan Naecker wrote:
> Hey there,
>
> I decided to reanimate this post cause I thought it was the easiest way
> to reference it. I hope somebody still have an eye on it, because I have
> the some problem, not for the Tomcat but for the JBoss AS.
>
> I think I understood that there is a context root and a deployment
> folder. The context root is part of the URL to access the web
> application. The deployment folder is the folder that JBoss uses to
> serve the requests for that application.
>
> But after changing for example context root of project A to B, I still
> have to enter http://localhost:8080/A to access it.
>
> So, how can I set a context root different from the Eclipse project name?
>
> Stephan
The problem is that the JBoss server adapter within WTP relies on
auto-deployment to serve the webapp. This means the context root for
the webapp is determined by the name of the WAR file created, which is
derived from the deploy-name. If you don't want to rename the project,
you can add the Web project to an EAR project. In the application.xml
of the EAR project, an alternate name for the webapp can be specified.
Deploy the EAR project and you can access the webapp with the alternate
context root. You might also try the JBoss AS Tools. The JBoss server
adapter it provides is better integrated and likely doesn't have this
problem.
Cheers,
Larry
|
|
|
|
Re: Context Root ignored? [message #557733 is a reply to message #540802] |
Wed, 08 September 2010 11:51  |
Eclipse User |
|
|
|
Sorry to necro this thread but it is exactly what i am dealing with.
I need to be able to change the behavior of publish to use the context root as the war file name instead of the project name. I am publishing to Resin using the resin plugin, but the resin plugin is just using the default publish behavior.
I hate to say it, but it wasn't the smartest way to set this up. In a large environment, more often than not, internal project names won't match the web root context. If the default publish behavior can be changed, fine, but it certainly is not obvious where to do that.
This is one of those choices that needs to be part of the project settings. Please advice on how to make that change.
|
|
|
Powered by
FUDForum. Page generated in 0.10390 seconds