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
messageComposite.setLayout( messageLayout );
		messageArea = new DialogMessageArea( );
		messageArea.createContents( messageComposite );
		titleImage = new Label( messageComposite, SWT.LEFT );
		FormData imageData = new FormData( );
		imageData.right = new FormAttachment( 100 );
		imageData.top = new FormAttachment( 0 );
		imageData.bottom = new FormAttachment( 100 );
		titleImage.setLayoutData( imageData );
		FormData messageData = new FormData( );
		messageData.left = new FormAttachment( 0, 0 );
		messageData.right = new FormAttachment( titleImage, 0 );
		messageData.bottom = new FormAttachment( titleImage, 0, SWT.BOTTOM );
		messageData.top = new FormAttachment( 0, 0 );
		messageArea.setTitleLayoutData( messageData );
		messageArea.setMessageLayoutData( messageData );
		return messageComposite;
	}
	
	private final boolean showPage( PropertyNode node )
	{
		if ( currentNode != null )
		{
			
			if ( node == currentNode || !currentNode.getPage( ).canLeave( ) )
			{
				return false;
			}
		}