From 2da80d923f608de2723b40b409a07387deecbec7 Mon Sep 17 00:00:00 2001 From: Luc Boudreau Date: Thu, 5 Aug 2010 14:58:22 +0000 Subject: [PATCH] Documented the test.properties file a little more. git-svn-id: https://olap4j.svn.sourceforge.net/svnroot/olap4j/trunk@337 c6a108a4-781c-0410-a6c6-c2d559e19af0 --- test.properties | 33 ++++++++++++++++++++++++--------- 1 file changed, 24 insertions(+), 9 deletions(-) diff --git a/test.properties b/test.properties index 2cdd681..6db4fd5 100644 --- a/test.properties +++ b/test.properties @@ -6,12 +6,10 @@ # All Rights Reserved. # You must accept the terms of that agreement to use this software. # -########################################################################################## +############################################################################### # This is the default repo file to allow CI builds to function properly. # Please do not commit any changes on it. # -# If you want to test olap4j against a different database, you should -# edit the jdbc.properties file in the simple-jndi folder. # # SPECIAL NOTE. # If the TCK is launched within Ant, the default amount of memory that @@ -19,20 +17,37 @@ # to perform and it is strongly suggested to give at lease 1 gig of ram # to Ant in order to run properly. You can easily achieve this by setting # ANT_OPTS environment variable to "-Xmx1024m". -########################################################################################## - -org.olap4j.test.connectUrl=jdbc:mondrian:Datasource=jdbc/SampleData;Catalog=./foodmart/FoodMart.xml; +############################################################################### +############################################################################### # This activates the Mondrian in-process tester. +# It is the default in-process Mondrian tester. +# By default, it will use a file based HSQLDB in the +# /foodmart folder. If you want to test olap4j against +# a different database, edit the jdbc.properties file +# in the /simple-jndi folder. + org.olap4j.test.helperClassName=org.olap4j.MondrianTester +org.olap4j.test.connectUrl=jdbc:mondrian:Datasource=jdbc/SampleData;Catalog=./foodmart/FoodMart.xml; + +############################################################################### +# These two lines activate the XMLA tester. Uncomment the two +# lines below to activate it. Make sure you comment out all others. +# The in-process XML/A tester is a memory hog. Read the comment above. +# By default, it will use a file based HSQLDB in the +# /foodmart folder. If you want to test olap4j against +# a different database, edit the jdbc.properties file +# in the /simple-jndi folder. -# These two lines activate the XMLA tester. Comment the line -# above and uncomment the two elow to activate it. #org.olap4j.test.helperClassName=org.olap4j.XmlaTester #org.olap4j.XmlaTester.CatalogUrl=file:foodmart/FoodMart.xml +############################################################################### # These options are used to test against a remote XML/A server. -# The server must have the FoodMart schema installed. +# Uncomment those properties and comment out the others above to +# activate it. The server must have the FoodMart schema installed. +# Both the data and the schema can be found in /foodmart + #org.olap4j.test.helperClassName=org.olap4j.RemoteXmlaTester #org.olap4j.RemoteXmlaTester.JdbcUrl=jdbc:xmla:Server=http://localhost:8080/mondrian/xmla #org.olap4j.RemoteXmlaTester.Username=joe