[news.eclipse.technology.ldt] Re: JSR 45 and support for non-Java class

["Darin Wright" <Darin_Wright@xxxxxxxxxx>]

>
> I don't know whether Eclipse supports JSR-45, but it would be a useful
> starting point.

The Eclipse Java debugger does support JSR-45.

>
> The current CVS version of Kawa (http://www.gnu.org/software/kawa)
> generates JSR-45-style SourceDebugExtension attributes.
> Kawa is a framework to compile various high-level languages (Scheme,
> XQuery, XPath, Emacs Lisp, and small subsets of XSLT and Common Lisp)
> directly into bytescodes, together with an associated run-time system.
> These are languages people think of as "interpreted" but they're actually
> compiled just like Java is, including line number and local variable
> attributes.  So there is no reason why Eclipse can't debug say a Scheme
> file, setting breakpoints, viewing stack traces etc.

The Java debugger provides API for creating breakpoints in a particular 
stratum.

@see JavaDebugModel.createStratumBreakpoint(..) and 
IJavaStratumLineBreakpoint.

>
> But Eclipse gets confused and acts dumb.  A stack trace will list a
> foo.scm - but not the line number, and clicking on the stack trace
> won't bring up the Scheme window.  This is annoying, and the sort
> of thing that needs to be fixed.  I had hoped that adding the
> SourceDebugExtension attribute would help, but it doesn't seem to make a 
> difference.

In a similar scenario when testing with JSPs, the Java debugger will bring 
up source for a JSP file. You have to be sure that the source lookup path 
knows where to search for your source files.

Darin Wright