Community
Participate
Working Groups
Right now we use a javaagent to instrument classes on the fly, injecting them with the SMAP data. This won't work when we don't control the launch, such as code running on a web server. We need to change a couple things: 1. Add a new builder that adds SMAP data to the .class files on disk. 2. Implement some sort of listener that sits around checking for debug events, wrapping IJavaDebugTargets when they're created.
Added SMAPBuilder.java and DebugTargetWrapper.java to handle what was described in the original comment. Also added another hard-coded filter "org.apache."to get rid of about 20 stack frames when debugging a service on Tomcat. EclipseEGL2Java adds the SMAPBuilder to the target project if necessary. The "Debug As > EGL Java Application" has been removed, now you just use the regular "Debug As > Java Application" and you'll get EGL debugging capabilities automatically.
Verified