[srau]

Hi – We have to switch between multiple webapp projects when we are developing. Unfortunately, all are called ROOT since we have to deploy our apps to the $TOMCAT_HOME/webapps/ROOT directory. This is a **major** problem for us.

Ideally, we would like have different names for our projects and deploy to ROOT. Is there a way around this ? Or is this problem going to be fixed soon ? If not, we just cannot use this product at this time. Please let us know.

Thanks

S Rau

[Scott Anderson]

Ideally, we would like have different names for our projects and deploy to ROOT. Is there a way around this ?

Right now, short of using separate workspaces (which would work), I can’t think of one.

Or is this problem going to be fixed soon ?

Absolutely. We recognize what a problem this is and it will be addressed in the GA release on 7/15. At that time, web projects will deploy in a directory named for the context root you’ve selected, thus giving you the capability you need.

Sorry for the inconvenience. We just ran out of time in the EA2 development schedule before we could get this put in properly. So many features, so little time. 🙂

–Scott
MyEclipse Support

[srau]

Thanks for the fast response – appreciate it. One more thing about the forthcoming fix – when we switch between projects (all deploying to the ROOT directory), will the IDE un-deploy the old binaries and re-deploy the new ones ?

Or do we have to explicitly undeploy the webapp in ROOT, change projects and redeploy ?

Also, will the plugin modify the server.xml context when this is done ?

Thanks again
S Rau

[Scott Anderson]

when we switch between projects (all deploying to the ROOT directory), will the IDE un-deploy the old binaries and re-deploy the new ones ?

Or do we have to explicitly undeploy the webapp in ROOT, change projects and redeploy ?

When you switch, the projects need to be undeployed as you go between them. In the first implementation, you’ll have to do this manually, so when you switch it will need to be an undeploy of the old project and then a deploy of the new project.

Also, will the plugin modify the server.xml context when this is done ?

Actually, server.xml won’t need to be modified at all since we’ll be deploying each project to the specially named ‘ROOT’ folder in the Tomcat deployment directory.

–Scott
MyEclipse Support

[srau]

Does the MyEclipse integration allow setting project specific properties which get passed in to the webapp at runtime ? eg., something like -Dapp.home=c:\devel

Each project would have a different app.home parameter.

Thanks
S Rau

[Scott Anderson]

At present, project specific property settings are not supported. It’s certainly an interesting enhancement though. As a workaround, could you have your apps look for -D<appname>.home=<whatever>? That way you could configure the server to pass all the args through and the application would each pick up the appropriate one.

–Scott
MyEclipse Support

[Author]

Posts