167376 – WSDM Tooling: No proper validation done for MRT and DDE files when user defined capability/MRT is removed from MRT/DDE

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

Bug 167376 - WSDM Tooling: No proper validation done for MRT and DDE files when user defined capability/MRT is removed from MRT/DDE

Summary: WSDM Tooling: No proper validation done for MRT and DDE files when user defin...

Status:	RESOLVED DUPLICATE of bug 167374

Alias:	None

Product:	z_Archived
Classification:	Eclipse Foundation
Component:	TPTP.monitoring (show other bugs)
Version:	unspecified
Hardware:	PC Windows XP

Importance:	P3 major (vote)
Target Milestone:	---
Assignee:	Andrew Eberbach
QA Contact:

URL:
Whiteboard:
Keywords:

Depends on:
Blocks:

Reported:	2006-12-11 00:09 EST by Balan Subramanian
Modified:	2010-06-03 15:03 EDT (History)
CC List:	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 Balan Subramanian

2006-12-11 00:09:03 EST

1. Create a new default Capability (new_file.cap)
   2. Create a new default MRT file and select new_file.cap file in to the default mrt file (new_file.mrt)
   3. Create a new default dd file and select new_file,mrt file in to the dd file (my.dd)
   4. Remove the new_file.mcap file
   5. Now reopen the New_file.mrt file, No system defined capabilities are shown in the editor 
   6. Now reopen the my.dd file,  it throws below exception
                                        java.lang.NullPointerException
	at org.eclipse.tptp.wsdm.tooling.editor.dde.util.internal.LoaderUtil.isExists(LoaderUtil.java:243)
	at org.eclipse.tptp.wsdm.tooling.editor.dde.util.internal.LoaderUtil.synchronizeMRTandResourceType(LoaderUtil.java:205)
	at org.eclipse.tptp.wsdm.tooling.editor.dde.util.internal.LoaderUtil.loadResourceTypeTable(LoaderUtil.java:177)
	at ..........

Comment 1 Balan Subramanian

2006-12-11 02:16:59 EST

duplicate of 

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