Some Eclipse Foundation services are deprecated, or will be soon. Please ensure you've read this important communication.
Bug 347274 - [code snippet] ClassNotFoundException while calling the constructor of an inner class through display view
Summary: [code snippet] ClassNotFoundException while calling the constructor of an inn...
Status: CLOSED WONTFIX
Alias: None
Product: JDT
Classification: Eclipse Project
Component: Core (show other bugs)
Version: 3.7   Edit
Hardware: PC Windows XP
: P3 normal (vote)
Target Milestone: ---   Edit
Assignee: JDT Core Triaged CLA
QA Contact: Ayushman Jain CLA
URL:
Whiteboard: stalebug
Keywords:
Depends on:
Blocks:
 
Reported: 2011-05-26 05:29 EDT by Satyam Kandula CLA
Modified: 2020-04-11 14:49 EDT (History)
1 user (show)

See Also:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Satyam Kandula CLA 2011-05-26 05:29:02 EDT
In the given test case, if I break in main() and then execute that statement (could not resolve type: pkg.X<String>$Y) from the display view, I get a ClassNotFoundException followed by the message "could not resolve type: pkg.X<String>$Y" 
########
package pkg;
public class X<T> {
	public class Y {
		String k;
		public Y(String kp) {
			k = kp;
		}
		public String getK() {
			return k;
		}
	}
	T field;
	public X(T param) {
		field = param;
	}
	public static void main(String [] args) {
		new X<String>("Hello").new Y("Hello").getK();
	}
}
########
This works good if X is not parameterized.
Comment 1 Satyam Kandula CLA 2011-05-26 05:37:40 EDT
(In reply to comment #0)
The statement that I executed from the display view is - 'new X<String>("Hello").new Y("Hello").getK();' and not 'could not resolve type: pkg.X<String>$Y' as stated in comment 0.
Comment 2 Eclipse Genie CLA 2020-04-11 14:49:14 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. As such, we're closing this bug.

If you have further information on the current state of the bug, please add it and reopen this bug. 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.