Summary: | ClassFileCompilationUnit should implement IClassFile | ||
---|---|---|---|
Product: | [Eclipse Project] JDT | Reporter: | Kai-Uwe Maetzel <kai-uwe_maetzel> |
Component: | Core | Assignee: | Philipe Mulet <philippe_mulet> |
Status: | RESOLVED WONTFIX | QA Contact: | |
Severity: | blocker | ||
Priority: | P3 | CC: | douglas.pollock |
Version: | 2.0 | ||
Target Milestone: | 2.0 M4 | ||
Hardware: | PC | ||
OS: | Windows 2000 | ||
Whiteboard: |
Description
Kai-Uwe Maetzel
2002-03-11 06:07:38 EST
This is the fake working copy for consistent usage of #getWorkingCopy. Why do you want it to implement IClassfile ? Ok to close ? 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. 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 ? Adding #getOriginalElement() implementation on ClassFileWorkingCopy Closing *** Bug 110945 has been marked as a duplicate of this bug. *** |