Bug 201673 Data Set Editor should not generate Parameter Position for an Named ODA Parameter
It is valid for an ODA data set parameter definition to have a driver-defined (native) name and no position (value = 0). The Data Set Editor currently assumes that this is not valid. It should *not* have automatically assign a derived position ( >0 value) to the data set parameter and issue a user warning message. The warning message in this case is inaccurate. And by assigning a bogus parameter position, it may disable the ability for the Data Engine to use the parameter's native name when interacting with the ODA runtime driver.
data/org.eclipse.birt.data/src/org/eclipse/birt/data/engine/executor/ParameterMetaData.java
}
    /* (non-Javadoc)
     * @see org.eclipse.birt.data.engine.odi.IParameterMetaData#getPosition()
     */
    public int getPosition()
    {
        return m_odaMetaData.getPosition();
    }
    /* (non-Javadoc)
     * @see org.eclipse.birt.data.engine.odi.IParameterMetaData#getValueClass()
     */
    public Class getValueClass()
    {
        
        return DataTypeUtil.toTypeClass( m_odaMetaData.getDataType() );
    }
    /* (non-Javadoc)
     * @see org.eclipse.birt.data.engine.odi.IParameterMetaData#isOptional()
     */
    public Boolean isOptional()
    {
        return m_odaMetaData.isOptional();
    }
    /* (non-Javadoc)
     * @see org.eclipse.birt.data.engine.odi.IParameterMetaData#getDefaultInputValue()
     */
    public String getDefaultInputValue()
    {
        return m_odaMetaData.getDefaultValue();
    }