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
}
	
	private void throwAdapterException( String methodName, Throwable cause ) 
		throws DataException
	{
		sm_logger.logp( Level.SEVERE, sm_className, methodName,
			"Cannot load DTP-to-BIRT ODA adapter." );
		
		throw new DataException( ResourceConstants.CANNOT_LOAD_ODA_ADAPTER, cause,
			new Object[] { m_dataSourceDriverId, ODA_ADAPTER_PLUGIN_ID } );
	}
	
	private ExtensionManifest throwConfigException( String methodName, 
	        		String dataSourceDriverId, Throwable cause ) 
		throws DataException
	{
		sm_logger.logp( Level.SEVERE, sm_className, methodName,
			"Cannot process data source extension configuration.", cause );
		
		throw new DataException( ResourceConstants.CANNOT_PROCESS_DRIVER_CONFIG, cause, 
			new Object[] { dataSourceDriverId } );	
	}
	
    /*
     * Gets the driver's trace logging element in plug-in manifest.
     */ 
	private TraceLogging getLoggingElement()
    {
	    final String methodName = "getLoggingElement";