Add to your JAVA_OPTS:
Or wherever your directory is located. However, the actual generated source will appear several directories down. I'm not sure if this is the desired effect.
I'm in a similar boat- while I've made some progress, I'm not quite there yet, i.e. I can't yet step into my JSP/Servlet code.
The Lomboz web site has the information that got me started
(http://www.objectlearn.com/support/docs/debuggingJSP.jsp), but it's absolutely minimal, and I couldn't find much help in the JBoss ($99 annual subscription) docs either!
I modified the entry for jasper JSP servlet in the file webdefault.xml under \server\all\deploy\jbossweb.sar:
That helped - except it put the generated servlet code under JBossHome/bin/JspServletSrc (so the scratchdir param seems to be relative to the JBoss bin directory).
One problem in debugging the generated servlets is eclipse is that they are under the org.apache.jsp package but the generated directory structure does not mirror the package structure. However, the problem was fixed by downloading and installing the Sysdeo patch for Tomcat plugin from here
Just make sure the zip file is before the Jasper compiler in the JBoss server's runtime classpath.
I even added the following entry to jboss-web.xml, under
(note, backslashes for the windows file system):
That didn't seem to do anything at all.
If you can figure out how to make the generated classes go under the eclipse workspace automatically, please let me know!