Bug 11086 - ClassFileCompilationUnit should implement IClassFile
Summary: ClassFileCompilationUnit should implement IClassFile
Status: RESOLVED WONTFIX
Alias: None
Product: JDT
Classification: Eclipse Project
Component: Core (show other bugs)
Version: 2.0   Edit
Hardware: PC Windows 2000
: P3 blocker (vote)
Target Milestone: 2.0 M4   Edit
Assignee: Philipe Mulet CLA
QA Contact:
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2002-03-11 06:07 EST by Kai-Uwe Maetzel CLA
Modified: 2005-09-28 11:54 EDT (History)
1 user (show)

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 Kai-Uwe Maetzel CLA 2002-03-11 06:07:38 EST 
It is implementing ICompilationUnit.
Comment 1 Philipe Mulet CLA 2002-03-11 10:47:52 EST 
This is the fake working copy for consistent usage of #getWorkingCopy.
Why do you want it to implement IClassfile ?
Comment 2 Philipe Mulet CLA 2002-03-12 08:55:40 EST 
Ok to close ?
Comment 3 Kai-Uwe Maetzel CLA 2002-03-12 09:36:17 EST 
A buffer factory registered with class files gets an ICompilationUnit as buffer 
owner passed into createBuffer. This is counter intuitive and does not allow 
access to the class file. JDT UI needs the class file to distinguish between 
class files in jars and those on the file system.
Comment 4 Philipe Mulet CLA 2002-03-13 13:21:49 EST 
So what ? The API #getWorkingCopy() should answer an IWorkingCopy. A working 
copy doesn't know about classfiles. You had the classfile in your hands before 
asking for the working copy...

We could however have its #getOriginalElement() return the classfile... would 
it do the trick ?
Comment 5 Philipe Mulet CLA 2002-03-14 13:27:47 EST 
Adding #getOriginalElement() implementation on ClassFileWorkingCopy
Comment 6 Philipe Mulet CLA 2002-03-19 10:22:28 EST 
Closing
Comment 7 Tom Hofmann CLA 2005-09-28 11:54:13 EDT 
*** Bug 110945 has been marked as a duplicate of this bug. ***