Bug 43877 - Need to open Java Editor on a memory-only Working Copy
Summary: Need to open Java Editor on a memory-only Working Copy
Status: ASSIGNED
Alias: None
Product: JDT
Classification: Eclipse Project
Component: Text (show other bugs)
Version: 3.0   Edit
Hardware: All All
: P5 enhancement (vote)
Target Milestone: ---   Edit
Assignee: JDT-Text-Inbox CLA
QA Contact:
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2003-09-29 17:42 EDT by Min Idzelis CLA
Modified: 2007-06-22 10:01 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 Min Idzelis CLA 2003-09-29 17:42:24 EDT 
Somehwere in 2.0+ the Eclipse API's were modified to allow a WorkingCopy to be
created without an underlying file. I am doing this, and I would like to open an
editor on this purely in memory file. However, when I try to open the purely in
memory WorkingCopy using JavaUI::openInEditor(), I get a dialog saying that the
file has been deleted on disk - Do you want to save or delete? 

I did some tracing, and found out that during opening, the method
AbstractTextEditor::validateEditorInputState is called, which eventually calls
AbstractTextEditor::sanityCheckState() and that's where the problem lies. 

I can't be very detailed right now since I've been using an (very ungly)
workaround for while, but I think it had something to do with the timestamps not
matching on the pure in memory working copy. 

I'd really like to see this fixed somewhere before 3.0 final is released.
Comment 1 Dani Megert CLA 2003-09-30 03:59:06 EDT 
The Java editor either uses a file editor based input or a storage based input
(for class files). It can't work with a working copy that has not file. This is
consistent to all other Java views. There are currently no plans to open the
Java editor in that area.
Comment 2 Dani Megert CLA 2007-06-22 09:59:35 EDT 
Get rid of deprecated state.