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.
UI/org.eclipse.birt.report.designer.ui/src/org/eclipse/birt/report/designer/data/ui/property/AbstractPropertyDialog.java
protected boolean isTitleVisible( )
	{
		return true;
	}
	/*
	 * (non-Javadoc)
	 * 
	 * @see org.eclipse.birt.report.designer.ui.dialogs.properties.IPropertyPageContainer#setMessage(java.lang.String,
	 *      int)
	 */
	public final void setMessage( String message, int messageType )
	{
		if ( messageArea != null )
		{
			if ( messageType != IMessageProvider.NONE )
			{
				titleImage.setVisible( false );
			}
			else
			{
				titleImage.setVisible( true );
			}
			messageArea.updateText( message, messageType );
		}
	}
	/**
	 * Convenience method to set a message with the message type
	 * IMessageProvider.NONE. It in turn calls the
	 * {@link #setMessage (String, int) setMessage}method.
	 *