- This topic has 25 replies, 13 voices, and was last updated 19 years, 11 months ago by
.
-
Posts
-
I would like to see the ability to have multiple web contexts in one project or at the very least the ability to create multiple Web Module Projects with the same root directory. It would allow me to use the following directory structure where web_contexts mirrors the webapps directory in Tomcat.
<pre>
/modules_root_dir
/java_src
/web_contexts
/context1
/WEB-INF
/context2
/WEB-INF
</pre>Hey Steve,
Actually a gentleman earlier HAD this setup and was running into some problem setting up the multiple projects he wanted to; to be fair, one of the problems is that Eclipse won’t allow 2 projects to have the same project root, but after a pretty long thread I think the ME team realized that there is some interest in getting support for this type of directory structure that may house many webroots (meaning many root dirs that would typically live under the webapps dir in Tomcat).So rest assured there are others that want this and I think come Jan/Feb we could start reevaluating the next-year plans for ME.
Happy Holidays!
-99 🙂
Since I regard ONE web application as ONE unit, there should be ONE project per web application.
If you really need some kind of master project (dunno why), create that as a resource project and use links to reflect this structure.
flames accepted.
NOP
Hah, quick someone vote +99!
Unfortunately NOP this isn’t a perfect world and I see most of the people request this, needing to deal with existing source trees and project structures at companies that were established a long time ago.
… the world is full of miracles…
… one is: CVS makes changes of old and overcome structures so easy:One person performs the changes, even moves folders in the CVS tree.
All other simply check this out, work with this and are happy!… too easy?
NOP
__
not operational at allI would love to be able to setup multiple web contexts for one project as well due to the current state of the code at my job.
As I understand it the request is for MyEclipse to support a web-project that can contain multiple web apps, i.e., multiple units of deployment. I believe NOP has a view consistent with the MyEclipse dev team that a ME web-project is a single unit of deployment, i.e., a single web app. As NOP suggested our consulting team uses CVS modules for this purpose. Does this work or is there really a need to have multiple webapps managed and deployed from within a single ME web project?
Now some issues that we discussed when deriving the current 1 ME web-project == 1 web app. The overriding concern is design/code time classpath isolation to simulate the isolation provided by a web container. This concern led to the current ME design that separations enterprise, EJB, and web projects. So I don’t see an easy way without some serious Eclipse JDT modifications to provide container-like isolation between web apps.
We are tightening up plans to increase web-project flexibility in an upcoming release. Planned enhancement include:
1) Allow a web-project folder to serve as web-root folder
2) Support linked resources, folders & files
3) Support multiple web-content folders
4) Allow WEB-INF folder to reside separate from web-content foldersI’m thinking that #1 & #2 will support a direct 1-1 mapping between webapp structure and ME web-project structure. This seems to be a move in the right direction without requiring any CVS restructuring if your codebase is organized around a Tomcat/webapps like structure.
Well, maybe I need to rethink my build frame of mind. However, let me explain why my development model might not quite fit the one webapp = one development unit concept.
The projects that I work on are generally small to medium sized. Often involving a public webapp, an admin webapp, an ejb-jar, and several JBoss SAR files all packaged into an EAR. I often am concurrently working on 3 or 4 of these projects at the same time. So for me a project fits better as a single unit of development.
If I broke each of the webapps, ejb-jars, sars, and the ear into individual development units for each of my projects it would quickly become an organizational nightmare.
Now I don’t expect MyEclipse to provide automated tools to help in building and managing my unique project structure. I also don’t want to be tied into any single IDE’s way to develop a project. So, I use ANT to build and package my project and to support my development tasks by generating, compiling, and deploying my app.
My point is that for whatever reason I use MyEclipse as an editor and debugger only and I use ant for everything else. So, although the general feature request may be to “Support multiple webapps in a single project” all that I really want is to be able to edit and debug jsps that may be located in different Web-app roots in the same eclipse project. I personally have no use for any of MyEclipse’s wizards, packaging, or deployment tools so simulating web app isolation is unimportant to me. If MyEclipse allows me to code assist a class that may or may not exist in my webapp I would look such a situation as a problem with my build script and not MyEclipse. In fact I would almost prefer all the webapps in my project to share the same classpath.
So perhaps the feature request was changed to:
“Be able to edit and debug jsps located in multiple webapps of the same project without regard for webapp isolation.”
The above request would 100% satisfy my desire for this feature. Perhaps this is all most of the people requesting this feature are looking for too? If the feature was simplified to my description above would that be more reasonable of a feature?
Mike
+1
This feature is mandatory!
We have sevaral web apps in our project, we currently use JIdea but I am evaluating Eclipse + MyEclipse.
JIdea has no problem to handle multiple web apps in a single project.
No multiple web contexts support is the only thing that makes me hesitate to switch to MyEclipse.What is the status for this feature request?
crazy,
I don’t know that its very high on our priority list right now although have you tried porting your project to MyEclipse using many Web Module Projects? Is the only contraint the issue of “shared resources”?We have done quite a bit of working to allow #1 and #2 above, also our deployment tool is a lot more intelligent now supporting the packaging and deployment of referenced Java Projects as well as external libraries; many users find this sufficient to work around previous limitations; however I understand this may not be optimal for you and your team.
Maybe you can give us more details about what limitation of ME is casuing you a headache and we can see what can be done about it?
