Bug 201379 Different process way for maxlevels 0 and maxrows 0[0003]
Description: Different process way for maxlevels and maxrows when they are set to 0 Build number:2.2.1.v20070828 Steps to reproduce: 1. Deploy BIRT. 2. set BIRT_VIEWER_MAX_ROWS as 0 3. set BIRT_VIEWER_MAX_CUBE_LEVELS as 0. 4. Preview report containing table and crosstab. Expected result: Same effect for these two properties Actual result: Return all rows for table and return 0 for crosstab Error log:n/a
data/org.eclipse.birt.report.data.adapter/src/org/eclipse/birt/report/data/adapter/impl/DataRequestSessionImpl.java
stopSign = new StopSign( );
		int mode = this.sessionContext.getDataEngineContext( ).getMode( );
		try
		{
			CubeMaterializer cubeMaterializer = null;
			if ( appContext == null )
				appContext = sessionContext.getAppContext( );
			if ( mode == DataEngineContext.DIRECT_PRESENTATION )
			{
				int size = 0;
				if ( appContext != null )
				{
					Integer value = DataTypeUtil.toInteger( appContext.get( DataEngine.IN_MEMORY_CUBE_SIZE ) );
					if ( value != null && value.intValue( ) > 0)
					{
						size = value.intValue( );
					}
				}
				cubeMaterializer = createCubeMaterializer( cubeHandle, size );
				createCube( (TabularCubeHandle) cubeHandle,
						cubeMaterializer,
						appContext,
						stopSign);
				cubeMaterializer.close( );
			}
			else if ( mode == DataEngineContext.MODE_GENERATION )
			{
				cubeMaterializer = createCubeMaterializer( cubeHandle, 0 );
				createCube(  (TabularCubeHandle)cubeHandle, cubeMaterializer, appContext, stopSign );
				cubeMaterializer.saveCubeToReportDocument( cubeHandle.getQualifiedName( ),