Bug 133096 Mapping of ODA data type literal value to code value
The ODA dataSource extension point specifies an ODA scalar data type in its literal value. But most handling of an ODA data type in the ODA framework is done with its code value. The oda.util.manifest package should provide the conversion utility to map from an ODA literal value to its corresponding code value. Another issue is with the native data type code. If a native data type is unknown, a 0 value has been used to represent "unknown" value. The latest implementation in the ODA design-time framework should be consistent with the definition.
data/org.eclipse.birt.data/src/org/eclipse/birt/data/engine/odaconsumer/Driver.java
private static final String ODA_ADAPTER_PLUGIN_ID = "org.eclipse.birt.data.oda.adapter.dtp";
    
    
	private static final String sm_className = Driver.class.getName();
	private static final String sm_loggerName = ConnectionManager.sm_packageName;
	private static LogHelper sm_logger = LogHelper.getInstance( sm_loggerName );
	Driver( String dataSourceElementId )
	{
		final String methodName = "Driver";		
		sm_logger.entering( sm_className, methodName, dataSourceElementId );
		m_dataSourceDriverId = dataSourceElementId;
		sm_logger.exiting( sm_className, methodName, this );
	}
	/**
	 * Returns the manifest that should be passed to 
	 * the ODA consumer helper to handle, 
	 * either a DTP ODA driver or the DTP-to-BIRT adapter.
	 */ 
	ExtensionManifest getExtensionConfig() throws DataException
	{
		if ( m_adapterConfig != null )
	        return m_adapterConfig;
		
		
		ExtensionManifest driverManifest = getDriverExtensionConfig();
	    assert( driverManifest != null );	
		
	    if ( m_adapterConfig != null )	
	        return m_adapterConfig;
	    return driverManifest;