|Re: [wtp-dev] Nashorn Debugging|
On 17 Mar 2015, at 12:16, Harald Wellmann wrote:
Yes, that's just the stuff I'd found out for so far (i.e. DebuggerSupportaccording to JDK-8044798), see my first message. I've also looked atNetBeans sources to get an understanding of how to gather of script sourceline info by tracking ClassPrepare events forjdk.nashorn.internal.scripts.Script* classes. That looks like the easierpart of the story.
The harder part (at least for me) is how to fit this into the JDT and JSDT design. (I'm familiar with Eclipse plugin development in general, but notreally with J(S)DT details.)
I'm also learning in this area - might need to try grab a JDT guy to help ;)
sounds cool - so just to verify I grok it right - does this require user launch the debugger as a "nashorn launch" or will it work on any Java launched app that debugger gets
(Directly launching a *.js source like jjs does would be a different story, which I'm not considering for now.)
yeah thats different.
There were two issues:- JavaClassPrepareBreakpoint does not handle wildcards in class names. Ihad to extend this class.
because nashorn generates wildcars into the class names ? Maybe submit patch to JDT for that ?
sounds like another bugfix for JDT.
I think so - can you share your code somewhere ? Maybe push to gerrit ? /max
Back to the top