- This topic has 16 replies, 6 voices, and was last updated 18 years ago by
.
-
Posts
-
IntelliJ IDEA supports this functionality. You create a Web Module and in the settings you can map any directory to something called Path Relative to Deployment Root. So, for example, I have my TLD’s in a directory not under /WEB-INF but here I can map that directory to /WEB-INF/taglibs which is where my TLD’s are specified in my web.xml. This feature allows me to fully debug JSP’s and that’s something I’ve never been able to accomplish with Eclipse and clients that do not have their projects set up in exploded WAR format.
Several months ago I attempted to move to Eclipse w/ Web Tools and MyEclipse but their lack of a flexible project structure prevented me from doing so. I am a consultant and can not use any flavor of Eclipse due to this lack of functionality because I never know how my clients are going to have their project’s directories laid out. An IDE SHOULD NOT dictate how you lay out your project’s directories.
@support-rkalla wrote:
but we want support of JSP debugging an so on.
Understandable, but what I was asking was if you had or were currently using an IDE that supported JSP coding/debugging/autocomplete/etc. right now with your current project structure? I’m not aware of an IDE that would support it, that is why I’m asking. Obviously the point I’m driving at is that if no other IDE supports this setup, this will most likely signal to your team that if you want some nicer development tools you may need to reorgnize bits of the project.
I’d encourage you to try IntelliJ to see if it supported your configuration, next to us this is the other most flexible IDE I’ve seen with project structure. NetBeans, JBuilder and WSAD have fairly strict requirements on project structure and most all of them do not support any notion of packaging & deployment of projects.
In the end if reorganization simply isn’t possible then there isn’t too much we can do. The most problomatic thing being that the development version of your project doesn’t look anything like the deployment version; its hard (impossible?) for ME to do proper autocomplete, resource resolution and packaging when this is the case (same goes for other IDEs, although I don’t know the specifics so I can’t really comment).
An IDE SHOULD NOT dictate how you lay out your project’s directories.
We agree. We wrote a specification for the project layout for the WTP committee back in 2004 or so what was a set of meta-information, you had all these artficats like “Web Root” and “WEB-INF directory” and so on, and you mapped those to physical locations, regardless of where they were. The idea was that WTP would implement this spec and we would all adopt it since all the Eclipse-based web IDEs are normalizing on WTP as the platform so to a certain degree we all interact with each other. That didn’t end up being the case and we are waiting to see if this does become the case in the 2.0 release before we completely adopt the project structure. At the end of the day we don’t care where the solutions are comming from, we just want to make our customers live’s easier.
