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

Bug 213318

Summary:	Exported datapool is incorrect.
Product:	z_Archived	Reporter:	Paul Slauenwhite <paulslau>
Component:	TPTP	Assignee:	Paul Slauenwhite <paulslau>
Status:	CLOSED FIXED	QA Contact:
Severity:	critical
Priority:	P1	CC:	jerome.bozier
Version:	unspecified	Keywords:	plan
Target Milestone:	---
Hardware:	All
OS:	All
Whiteboard:

Description Paul Slauenwhite

2007-12-18 10:47:59 EST

Exported datapool with deleted variables is incorrect.

Steps to reproduce:

1) Create a datapool with three variables.
2) Add two or more rows to the equivalence class.
3) Delete two of the rows.
4) Export the datapool.
5) Note, the exported datapool contains the data for all three variables and the variable declarations for two of the variables.

Comment 1 Paul Slauenwhite

2007-12-18 10:48:33 EST

Jerome B, please investigate.

Comment 2 Paul Slauenwhite

2007-12-18 10:50:39 EST

For example:

,Variable1::String,Variable2::String
EquivalenceClass1::0,1,2
EquivalenceClass1::1,1,2


Note, the two EquivalenceClass1.

Comment 3 Paul Slauenwhite

2008-01-30 12:14:36 EST

Deferred from I5 to I6 with PMC approval.

Comment 4 Paul Slauenwhite

2008-03-04 13:09:33 EST

This defect is not limited to removing variables from the datapool.  Any changes to the datapool in the Datapool Editor after the datapool is first loaded have the same effect.  The changes made in the Datapool Editor are saved but the export wizard is loading all the datapool files in the workspace using a static instance of a resource set (org.eclipse.hyades.test.core.util.EMFUtil.resourceSet) causing the load to default to the existing loaded instance, which is of course stale after the save of the Datapool Editor.

The follow class checked in to CVS (HEAD):

org.eclipse.hyades.test.ui.dialog.EObjectResourceContentProvider.java

Comment 5 Paul Slauenwhite

2008-03-04 13:11:03 EST

(In reply to comment #2)
> For example:
> 
> ,Variable1::String,Variable2::String
> EquivalenceClass1::0,1,2
> EquivalenceClass1::1,1,2
> 
> 
> Note, the two EquivalenceClass1.
> 

This is working as designed since the EquivalenceClass1 has two variables with two records (0 and 1).

Comment 6 Paul Slauenwhite

2008-06-10 09:59:47 EDT

Verified in TPTP-4.5.0-200806070100.  Closing.