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

Bug 339154

Summary:	ODA DataSourceDesign attribute could be optional in a nested DataSetDesign
Product:	[Tools] Data Tools	Reporter:	Linda Chan <lchan>
Component:	Open Data Access	Assignee:	Linda Chan <lchan>
Status:	RESOLVED FIXED	QA Contact:
Severity:	normal
Priority:	P3
Version:	1.8.1
Target Milestone:	1.9
Hardware:	All
OS:	All
Whiteboard:

Description Linda Chan

2011-03-07 21:39:47 EST

Per the documentation of the org.eclipse.datatools.connectivity.oda.design model schema, a nested data set (of the data set parameters w/ DynamicValuesQuery) may either have a null data source, or contain a data source design instance.
"The instance of dataSourceDesign that supports this type of data set.  Could be null, if nested within another dataSetDesign, to share the container's dataSourceDesign."

The related EMF model implementation however has set the DataSourceDesign attribute as required, and would trigger a validation error when running a diagnostic on a DataSetDesign EObject.

Comment 1 Linda Chan

2011-03-08 18:04:41 EST

Revised the oda.design EMF model and diagnostic logic to allow a null DataSourceDesign referenced by a DataSetDesign that is set in a DynamicValuesQuery type object.
Tagged 1.9 branch with v201103090701.