Some Eclipse Foundation services are deprecated, or will be soon. Please ensure you've read this important communication.

Bug 354906

Summary: org.eclipse.debug.core.DebugException: while trying to view the object
Product: [Eclipse Project] JDT Reporter: Vijay <vijaymodak>
Component: DebugAssignee: JDT-Debug-Inbox <jdt-debug-inbox>
Status: CLOSED DUPLICATE QA Contact:
Severity: normal    
Priority: P3 CC: Michael_Rennie, pawel.1.piech, vijaymodak
Version: 3.3   
Target Milestone: ---   
Hardware: PC   
OS: Windows XP   
Whiteboard:
Attachments:
Description Flags
Attachment for the debug error none

Description Vijay CLA 2011-08-17 02:16:22 EDT 
Build Identifier: M20071023-1652

Using web service trying to capture some data 
WSDL version 2.0. created proxies for that WSDL and pushed in the web project by creating jar file.

AccountQuery accountQuery = new AccountQuery();
TeamQuery  accountTeamQuery = new TeamQuery();
accountTeamQuery.set**(some param);
ListOfTeamQuery listOfTeamQuery = new ListOfTeamQuery();
listOfTeamQuery .setTeam(accountTeamQuery);
accountQuery .setListOfTeam(listOfTeamQuery);

usine inputClient I submitted that request to web service.

getting proper output also (not throwing any exception)

but while trying to check the reponse object I am getting the exception 

org.eclipse.debug.core.DebugException: com.sun.jdi.ClassNotLoadedException: Type has 
not been loaded occurred while retrieving component type of array.

and this exception was common for other object also


Reproducible: Always
Comment 1 Vijay CLA 2011-08-17 02:23:45 EDT 
Created attachment 201616 [details]
Attachment for the debug error

for getting more idea attaching the image from eclipse debugger window
Comment 2 Vijay CLA 2011-09-20 01:36:58 EDT 
Please share any update or comment from Eclipse side ....
Comment 3 Michael Rennie CLA 2011-09-20 11:37:29 EDT 
(In reply to comment #2)
> Please share any update or comment from Eclipse side ....

Looks like a dupe of bug 182999. 

Please see the explanation on bug 182999 comment 8

*** This bug has been marked as a duplicate of bug 182999 ***