Bug 176569 123 is treated as Blank Value in Scalar Parameter [0705]
Description: 123 is treated as Blank Value in Scalar Parameter. Build number: 2.2.0.v20070307-1128 Steps to reproduce: 1. New a Parameter. 2. Untick Allow null value checkbox. Expected result: Parameter works correctly. Actual result: Another Parameter dialogue pops up and when you click OK button again, warning message "NewParameter cannot be blank" pops up (see the screenshot). Error log: N/A
viewer/org.eclipse.birt.report.viewer/birt/WEB-INF/classes/org/eclipse/birt/report/service/actionhandler/BirtCacheParameterActionHandler.java
Oprand[] op = this.operation.getOprand( );
		if ( op != null )
		{
			for ( int i = 0; i < op.length; i++ )
			{
				ConfigVariable configVar = new ConfigVariable( );
				String paramName = op[i].getName( );
				String paramValue = op[i].getValue( );
				if ( paramName == null || paramValue == null )
					continue;
				if ( paramName
						.equalsIgnoreCase( ParameterAccessor.PARAM_ISLOCALE ) )
				{
					
					locs.add( paramValue );
				}
				
				else if ( paramName
						.equalsIgnoreCase( ParameterAccessor.PARAM_ISNULL ) )
				{
					ParameterDefinition parameter = attrBean
							.findParameterDefinition( paramValue );
					if ( parameter != null )
					{
						
						configVar.setName( ParameterAccessor.PARAM_ISNULL
								+ "_" + parameter.getId( ) ); 
						configVar.setValue( paramValue
								+ "_" + parameter.getId( ) ); 
						handle.addConfigVariable( configVar );