Bug 40052 - DCR - Need opened API for determining associated source for class files
Summary: DCR - Need opened API for determining associated source for class files
Status: RESOLVED WORKSFORME
Alias: None
Product: JDT
Classification: Eclipse Project
Component: Core (show other bugs)
Version: 2.1   Edit
Hardware: All All
: P3 enhancement (vote)
Target Milestone: 3.0 M4   Edit
Assignee: JDT-Core-Inbox CLA
QA Contact:
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2003-07-14 15:10 EDT by Tan T Phan CLA
Modified: 2003-09-19 07:11 EDT (History)
0 users

See Also:

Attachments
Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.
Description Tan T Phan CLA 2003-07-14 15:10:06 EDT 
We need an opened API for a replacement Java editor to determine the associated
source for Java class files. Currently, I have to use the internal imports:

1. org.eclipse.jdt.internal.ui.javaeditor.IClassFileEditorInput
2. org.eclipse.jdt.internal.ui.javaeditor.InternalClassFileEditorInput
Comment 1 Olivier Thomann CLA 2003-09-16 14:13:52 EDT 
Why don't you use getSource() on the org.eclipse.jdt.core.IClassFile?
Comment 2 Philipe Mulet CLA 2003-09-19 07:11:22 EDT 
This is the official API to do so. Closing.
Please reopen if you found some issue with it.