Bug 132084 Inconsistent manifest data type for an ODA driver's native data type code
The ODA runtime extension point (org.eclipse.datatools.connectivity.oda.dataSource) schema has defined its dataTypeMapping.nativeDataTypeCode attribute to be an integer value. The oda.util.manifest package, which provides encapsulated access to an ODA runtime extension's plugin manifest, handles such attribute value as a "short" data type. It should be corrected to an "int", to be consistent with its schema definition.
data/org.eclipse.birt.data/src/org/eclipse/birt/data/engine/odaconsumer/Driver.java
}
		catch( UnsupportedOperationException ex )
		{
			sm_logger.logp( Level.SEVERE, sm_className, methodName,
					"Cannot get ODA data source driver factory.", ex );
			throw new DataException( ResourceConstants.INIT_ENTRY_CANNOT_BE_FOUND, ex, 
                                     new Object[] { m_dataSourceDriverId } );
		}
	}
	 
	
	int getTypeMapping( String dataSetType, int nativeType ) throws DataException
	{
	    final String methodName = "getTypeMapping";
		DataSetType dsType = null;
		
		try
		{
			dsType = getDriverExtensionConfig().getDataSetType( dataSetType );
		}
		catch( OdaException ex )
		{
			sm_logger.logp( Level.SEVERE, sm_className, methodName,
					"Cannot find data set element.", ex );
			throw new DataException( ResourceConstants.INVALID_DATA_SET_TYPE, ex );
		}
		DataTypeMapping mapping = dsType.getDataTypeMapping( (short) nativeType );
		
		
		if( mapping == null )