Hi Juergen, Thanks for the nice words and your considerations!
I would like to comment some statements: First, we are going to provide the OpenAPI allowing implementation of a "app-server integration" plugin. The plugin will be able to "teach" IDEA how to: 1. start the app server 2. map jsp line numbers to servlet line numbers and vice versa The API is currently being prepared for the opening. As a reference implementation of this API we will provide current Tomcat 4.0.4 integration (with the source code). Another implementation of the API we are going to provide, is JSR45-compatible app server integration. As for Tomcat 4.1.x support, I'm afraid we are out-of-luck here. Tomcat 4.0.4 used to generate useful comments in the servlet code, that allowed the integration plugin to map jsp line numbers to servlet line numbers. But from the new version of Tomcat (Jasper2 in particular), this functionality is missing. At least I haven't been able to find anything to enable comment generation, and nobody from Tomcat user-list answered my question about this. JRun4 claims to support JSR45, so now, when updated JPDA is available in JDK1.4.1 release, we are going to try again how the new stuff works. Previous attempts to make this work failed as I mentioned in my earlier posts. JSP validation currently uses Jasper from Tomcat 4.0.4, but it also will be pluggable, so implementing the required API will allow to use arbitrary compiler for JSP validation. As for the "show servlet" and "side-by-side" debugging features, why not posting them to our tracker :-) ? We'll consider them during the next version planning - the feature set for Ariadna is already frozen. -- Best regards, Eugene Zhuravlev JetBrains, Inc, http://www.intellij.com "Develop with pleasure!" "jürgen höller [werk3AT]" <[EMAIL PROTECTED]> wrote in message news:[EMAIL PROTECTED]... Dear JetBrains staff, Having been an IDEA 2.6 user for some time, I have just tried Build 647 to get an impression of the upcoming web app support. First of all, great work! Recognition of JSP includes, JSP compilation, Tomcat debugging - valuable enhancements to an already invaluable IDE :-) This kind of web app support is the one thing that I've been missing in IDEA! I have some knowledge of web app support in both NetBeans/Forte and JBuilder Enterprise. For a while, I've been using IDEA 2.6 and NetBeans on the same project: NetBeans only for JSP compilation and debugging, IDEA for everything else! My colleagues use JBuilder 5/6, but I've already convinced them to switch to IDEA ASAP. Finally, Ariadna will allow all of us to switch to IDEA, providing all the features we need in one single environment! Some additional features that I'd like to see in the final version, mainly stemming from NetBeans: - "Run" a WebApp, just like "Debug" a WebApp; - a "Show Servlet" command on a JSP that opens the servlet source generated by JSP compilation in the editor (to be able to inspect the generated code and see JSP compilation errors exactly in the servlet source instead of estimatedly in the JSP source); - side-by-side debugging of JSP source and generated servlet source, recognizing breakpoints and current lines in both (no special support in the editor, just "Show Servlet" while debugging, and allowing for breakpoints like in a normal servlet). I assume that all the compilation and runtime information necessary for the latter features already exists in Ariadna, so implementing them should be straightforward. Note that neither is provided by JBuilder - currently these are distinctive NetBeans features! Furthermore, I would like to see support for Tomcat 4.1.x and Jasper 2. By the time Ariadna will be released, Tomcat 4.1.10+ will not only be the recommended but also the mainly used Tomcat 4 release, replacing 4.0.4. So IMHO it would make sense to support 4.1.x from the beginning. Concerning other web containers: JRun 4 is fine but why is it favoured? IMHO providing tight support for Tomcat 4 (including using Jasper for JSP validation and precompilation) is enough for IDEA's standard distribution. Every other container can be debugged via JPDA if there's no IDEA plugin. You can include the servlets generated by your container in IDEA's sourcepath if you debug JSPs. So the two benefits of tight support for a certain container are: startup and shutdown via the IDE, and JSP source level debugging - nice, but not indispensable. Keep up the excellent work! Regards, Juergen _______________________________________________ Eap-features mailing list [EMAIL PROTECTED] http://lists.jetbrains.com/mailman/listinfo/eap-features
