- This topic has 5 replies, 4 voices, and was last updated 20 years, 9 months ago by
.
-
Posts
-
What is the best way to handle referenced projects to facilitate interactive debugging?
I have a project that contains several servlets. These servlets refer to other projects. These other projects handle things like database access and report generation and are used by other projects also.
A side from exporting jar files and adding them to the tomcat 5 application Paths entry, is there a way to have tomcat look into the workspace to resolve these references?
Ideas or suggestions?
Mike
Mike,
If you compile these utility projects into JARs, and then include those JARs in the deployment of your main webapp it will work fine (debugging).I currently am working on a library class that I use in a web application. I deploy the web application with the library’s JAR as part of the webapp. Then I go back and set breakpoints in the library and interacte with Tomcat and MyEclipse behaves as it should (stopping at breakpoints).
When you go to set breakpoints in your utility projects (the data access and report generation ones) if you see a checkmark in the blue ball marking the breakpoint, then that means the class is currently loaded by the web application server and will be properly loaded for debugging when the breakpoint is set. This is a good guide to know if things are on the up and up.
That is a solution, but it would be much better if tool could create and deploy utility project jar after I change source code in utility project(like in WebSphere Studio).
Filip
Filip,
You are absolutely right. There has been a huge request for this type of behavior and IIRC we are shooting for 2.8 for strong “dependant project” deployment support. I’ll double check with Scott/Michael about this.Yep, dependent project support is one of the big features for 2.8, so sooner rather than later. 🙂
