Some Eclipse Foundation services are deprecated, or will be soon. Please ensure you've read this important communication.
Bug 339154 - ODA DataSourceDesign attribute could be optional in a nested DataSetDesign
Summary: ODA DataSourceDesign attribute could be optional in a nested DataSetDesign
Status: RESOLVED FIXED
Alias: None
Product: Data Tools
Classification: Tools
Component: Open Data Access (show other bugs)
Version: 1.8.1   Edit
Hardware: All All
: P3 normal (vote)
Target Milestone: 1.9   Edit
Assignee: Linda Chan CLA
QA Contact:
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2011-03-07 21:39 EST by Linda Chan CLA
Modified: 2011-03-08 18:04 EST (History)
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 Linda Chan CLA 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 CLA 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.