Bug 200755 [smoke]Fail to preview Crosstab after deploy BIRT in application servers.[0601][1102]
data/org.eclipse.birt.report.data.adapter/src/org/eclipse/birt/report/data/adapter/api/DataRequestSession.java
import org.eclipse.birt.core.framework.PlatformConfig;
import org.eclipse.birt.data.engine.api.IBaseDataSetDesign;
import org.eclipse.birt.data.engine.api.IBaseDataSourceDesign;
import org.eclipse.birt.data.engine.api.IBasePreparedQuery;
import org.eclipse.birt.data.engine.api.IBaseQueryResults;
import org.eclipse.birt.data.engine.api.IDataQueryDefinition;
import org.eclipse.birt.data.engine.api.IPreparedQuery;
import org.eclipse.birt.data.engine.api.IQueryDefinition;
import org.eclipse.birt.data.engine.api.IQueryResults;
import org.eclipse.birt.data.engine.api.IResultMetaData;
import org.eclipse.birt.data.engine.api.querydefn.QueryDefinition;
import org.eclipse.birt.data.engine.olap.api.ICubeQueryResults;
import org.eclipse.birt.data.engine.olap.api.IPreparedCubeQuery;
import org.eclipse.birt.data.engine.olap.api.query.ICubeQueryDefinition;
import org.eclipse.birt.report.data.adapter.i18n.ResourceConstants;
import org.eclipse.birt.report.model.api.DataSetHandle;
import org.eclipse.birt.report.model.api.olap.CubeHandle;
import org.mozilla.javascript.Scriptable;
/**
 * Main entry point to Data Engine functionalities. Each data request session can be used
 * to execute data requests associated with one report design. 
 * 
 * The user of a data request session typically start by defining all data sources and data sets
 * available in the report design by calling the <code>defineDataSet</code> and 
 * <code>defineDataSource</code> methods. It can then call <code>prepare</code> to start preparing
 * queries for executions. 
 * 
 * This class is MT-safe. Multiple queries can be prepared at the same time by different threads.
 */
public abstract class DataRequestSession