Bug 160135 - [quick fix] fix for 'no enclosing instance accessible'
Summary: [quick fix] fix for 'no enclosing instance accessible'
Status: ASSIGNED
Alias: None
Product: JDT
Classification: Eclipse Project
Component: UI (show other bugs)
Version: 3.1.1   Edit
Hardware: PC Windows XP
: P3 normal (vote)
Target Milestone: ---   Edit
Assignee: JDT-UI-Inbox CLA
QA Contact:
URL:
Whiteboard: stalebug
Keywords:
Depends on:
Blocks:
 
Reported: 2006-10-08 00:16 EDT by Ralf Hauser CLA
Modified: 2022-08-25 13:43 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 Ralf Hauser CLA 2006-10-08 00:16:04 EDT 
Got <<No enclosing instance of type HttpHandler is accessible. Must qualify the allocation with an 
 enclosing instance of type HttpHandler (e.g. x.new A() where x is an instance of HttpHandler).>>

Tried to create a HttpHandler in the static part of the class where I did use the constructor of the "Response" class, but this did not work either

Therefore
1) eclipse probably knows what "A" is, in my case it was "Response", thus if you already know that x is HttpHandler why not say what A is?
2) as a quick fix, offer to move the A class into its own .java file such that the problem no longer occurs
...) probably there are other quick fixes...
Comment 1 Frederic Fusier CLA 2006-10-08 07:50:13 EDT 
These issues still occur in 3.2 and 3.3.
As the may one is for quick-fix, I keep this one for problem 2) and move to JDT/UI. Please, open another bug against JDT/Core for problem 1), thanks
Comment 2 Ralf Hauser CLA 2006-10-08 07:57:49 EDT 
done as per Bug 160147
Comment 3 Eclipse Genie CLA 2020-08-29 08:04:57 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 4 Eclipse Genie CLA 2022-08-25 13:43:35 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.