Bug 1622 - JavaDebugger.showInEditor should try to use ClassElement.Finder.
JavaDebugger.showInEditor should try to use ClassElement.Finder.
Status: CLOSED FIXED
Product: debugger
Classification: Unclassified
Component: Code
3.x
All All
: P4 (vote)
: TBD
Assigned To: Jan Jancura
issues@debugger
:
Depends on:
Blocks:
  Show dependency treegraph
 
Reported: 1999-04-30 00:29 UTC by Jesse Glick
Modified: 2003-06-30 17:26 UTC (History)
0 users

See Also:
Issue Type: DEFECT
:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Jesse Glick 1999-04-30 00:29:01 UTC
The debugger when displaying source code lines in the editor, currently looks up its guess at the Java source file name in the Repository, then finds the data object, gets the LineCookie, etc. Howev
er, as it hardcodes the .java extension, this will make it unable to debug any other types of source (e.g. other languages) that compile to bytecode and provide the Elements hierarchy.

Suggest that it instead use the new ClassElement.Finder to look up the proper class element that this class comes from. Then get the containing source element. Now try to find the data object providin
g this source element--probably the SourceElementImpl in the JDO module should have a DataObject cookie which would return the JDO, I think this would be natural. Then proceed as usual.

Or, use RemoteClass.getSourceFileName, although I think this gives only the filename and not package, so you would have to look for that filename in what you guessed was the right folder.
Comment 1 Quality Engineering 2003-06-30 17:26:16 UTC
Resolved for 3.3.x or earlier, no new info since then -> closing.


By use of this website, you agree to the NetBeans Policies and Terms of Use. © 2012, Oracle Corporation and/or its affiliates. Sponsored by Oracle logo