| Summary: | Support migration of oda.xml driver to the DTP Enablement namespace | ||
|---|---|---|---|
| Product: | z_Archived | Reporter: | Linda Chan <lchan> |
| Component: | BIRT | Assignee: | xingjie he <xhe> |
| Status: | RESOLVED FIXED | QA Contact: | |
| Severity: | enhancement | ||
| Priority: | P3 | CC: | bluesoldier, yli |
| Version: | 2.1.1 | ||
| Target Milestone: | 2.2.0 M2 | ||
| Hardware: | PC | ||
| OS: | Windows 2000 | ||
| Whiteboard: | |||
| Bug Depends on: | 156017 | ||
| Bug Blocks: | |||
|
Description
Linda Chan
DTE maybe will do it before 10.6, after they move the package , model will support it. now hold it. This bug need the DtE finish firstly. See bug 156017. BZ 156017 has been resolved since Oct. 3. Related changes have been included in BIRT 2.2 daily build.
To find out whether an oda data source is deprecated, and its replacing oda data source id, use its oda.util.manifest.ExtensionManifest.
Two related methods are now available:
public boolean isDeprecated()
public String getRelatedDataSourceId()
after 3.2.7, convert deprecated extension id to new one. fix it This bug has been fixed for a patch. However, problems remains: 1. Manifest only provides methods for data source. 2. Model should put calls to DTP classes into plugin subpackage. Above changes defer to M2. Added an optional sub-element to the dataSet element in the oda.dataSource extension point schema to define a data set relationship (Bugzilla 159093; DTP 1.0 M3). Added related methods in the oda.util.manifest.DataSetType to access the content of the associated relationship element.
To find out the replacing oda data set id, use its oda.util.manifest.DataSetType methods:
public boolean isDeprecated()
public String getRelatedDataSetId()
Fix it. Thanks Linda |