Some Eclipse Foundation services are deprecated, or will be soon. Please ensure you've read this important communication.
Bug 355936 - NPE in AbstractEditingModel.getInputStream
Summary: NPE in AbstractEditingModel.getInputStream
Status: CLOSED WONTFIX
Alias: None
Product: PDE
Classification: Eclipse Project
Component: UI (show other bugs)
Version: 3.7   Edit
Hardware: PC Windows 7
: P3 normal (vote)
Target Milestone: ---   Edit
Assignee: PDE-UI-Inbox CLA
QA Contact:
URL:
Whiteboard: stalebug
Keywords:
Depends on:
Blocks:
 
Reported: 2011-08-26 07:17 EDT by Nicolas Bros CLA
Modified: 2019-10-11 02:27 EDT (History)
2 users (show)

See Also:

Attachments
stacktrace (6.80 KB, text/plain)
2011-08-26 07:17 EDT, Nicolas Bros CLA 		no flags Details
View All 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 Nicolas Bros CLA 2011-08-26 07:17:45 EDT 
Created attachment 202218 [details]
stacktrace

I got a NPE trying to open a MANIFEST.MF (see attached stacktrace)
Comment 1 Nicolas Bros CLA 2011-08-26 07:18:11 EDT 
version:
Eclipse SDK
Version: 3.7.0
Build id: I20110613-1736
Comment 2 Curtis Windatt CLA 2011-08-26 10:40:23 EDT 
Can you provide more details about when this happens for you?

Looking at BuildInputContext (Line:51) it is possible to create a model for a null document, which is bad.  However, I don't see when we would end up with a null document for an existing storage editor input.
Comment 3 Nicolas Bros CLA 2011-08-26 11:21:45 EDT 
Sorry, I can't reproduce. It only happened once to me, and I don't remember exactly what I was doing right before the exception. It maybe happened when I copied a MANIFEST.MF to another project and then renamed it to "MANIFEST.MF.template". Maybe having two MANIFEST.MF at once confused PDE.
Comment 4 Eclipse Genie CLA 2019-10-10 13:36:02 EDT 
This bug hasn't had any activity in quite some time. Maybe the problem got resolved, was a duplicate of something else, or became less pressing for some reason - or maybe it's still relevant but just hasn't been looked at yet.

If you have further information on the current state of the bug, please add it. The information can be, for example, that the problem still occurs, that you still want the feature, that more information is needed, or that the bug is (for whatever reason) no longer relevant.

--
The automated Eclipse Genie.
Comment 5 Karsten Thoms CLA 2019-10-11 02:27:08 EDT 
Issue just happened once 8 years ago. Closing.