- This topic has 9 replies, 3 voices, and was last updated 19 years, 12 months ago by
.
-
Posts
-
Hi
I have a problem that I can’t seem to be able to find the best way to solve.
System Setup
=========
Windows XP Home Edition
Eclipse 3.0.1
MyEclipseIDE 3.8.2
Tomcat 5.0.28I have multiple web projects that I work on. They all need to be projects with no context path associated with them. Ie context path = /.
In the past when using tomcat in standalone mode I would create a host for each project and then within that host a context path of root or slash. Tthen each project could run simultaneously without interfering with each other.
When using MyEclipseIDE and its integration with tomcat, it seems to want to dump all projects to the default host and ROOT webapp folder. Is there any way or documentaion on the recommended way to deploy multiple apps beyond the quick and dirty deploy to ROOT.
Thank you so much for your feedback.
Kenneth Lancaster
Kenneth,
If you are telling MyEclipse that each of the 3 projects deploys to a context root of “/”, then yes everything will be deployed to ROOT. The ‘right’ way is to deploy each one during development to independent web app contexts:
/app1
/app2
/app3and then when you are ready to deploy to production, just copy your app out to the proper location in your app server install. Maybe I’m misunderstanding your question, because it sounds like you answered your own question…
I would have tried that… deploying to different contexts but the problem is that each of these legacy applications requires (bad) a context root of “\” or they will not work correctly. Yes, bad coding, I did not do it 🙂 But I am stuck with this issue since references to context root are all over the place. So I need to keep each application with a context root of “/”. How could I do this and still use MyEclipse
each of these legacy applications requires (bad) a context root of “\” or they will not work correctly.
Ohhh I see, I didn’t realize it was required (hard coded paths or something).
How could I do this and still use MyEclipse
Hrrm… I don’t think this is possible with the current version of MyEclipse. The reason I say that is we have a popular open enhancement for multiple deployments of the same project to different servers and multiple servers of the same type… neither of these enhancements have been addressed just yet but will likely be made available as part of a much larger sweeping change in the 3.9/4.0 time frame.
The only way I see for you to work around this right now is to use a custom ant script that has build/deploy targets for 3 seperate tomcat instances, each running on a different port or something like that so you can deploy your 3 apps at the same time out to each of the servers.
Thanks for your prompt response… It kept me from beating my head against the wall for a day.
So there is no to deploy to mutliple defined host in the same tomcat instance. The only host you can deploy to is whatever the default localhost happens to be?
Just to clarify:
Once you setup an app server, say Tomcat 5, that is the only instance of the Tomcat 5 connector you can use. If you have Tomcat 5.0.25, 27 and 28 installed on your system locally, you will have to configure the MyEclipse Tomcat 5 connector to point to one of them, the other two will be ignored. ONce you’ve done that, you can deploy any number of projects to that Tomcat install, but you cannot deploy a single project to more than one application server at a time. Also I believe MyEclipse will warn you when you have multiple projects open that all deploy to the same context root (/ for example) and the deployer will make you aware of the problem as well. You can close the offending projects to work around this so you are able to deploy all the projects to the same location ontop of eachother (deleting the previous inhabitent each time).
Hi,
I saw the announcement of the 3.8.3 release and was wondering…..
The enhancement #280 in the release notes ( https://www.genuitec.com/forums/topic/a-generic-application-server/#post-200229 ) does it finally solve the problem you clarified in the post above. It sound like it does not but maybe I did not understand it well.
Thanks
Ken Lancaster
Ken,
It solves the issue to a level since it allows you to deploy your project to whatever directory you’d like, rather than just the preconfigured connector locations. Of course when you do that extra server configuration will likely be required to tell the server how to load your application.
So is the above statement still accurate or has the request been moved up any 🙂
“The reason I say that is we have a popular open enhancement for multiple deployments of the same project to different servers and multiple servers of the same type… neither of these enhancements have been addressed just yet but will likely be made available as part of a much larger sweeping change in the 3.9/4.0 time frame. ”
Thanks
We have not added explicit direct support for multiple connectors of the same type. However, you can easily work around the issue by using either the new custom deployment locations or the new remote debugging support in 3.8.3, which will allow you to use any server you like, deploy as you see fit, and still get full Java and JSP debugging. Basically, for the advanced user we went for “full flexibility”. You can read more about how to use these features in the Remote Debugging Quickstart that is included in the MyEclipse Application Developer Guide in the product, or on the website in the Documentation section here:
http://www.myeclipseide.com/ContentExpress-display-ceid-67.html
