jshih

Try using utf-8 encoding to re-create your database (e.g., create database jasperserver character set utf8;), configuring tomcat to recognize utf-8 encoding (e.g. URIEncoding="UTF-8" in conf/server.xml), and defining jdbc connection accordingly (e.g., url="jdbc:mysql://localhost:3306/jasperserver? useUnicode=true&characterEncoding=UTF-8"). See the JasperServer-Localization-Guide for more details. Jenngang JasperSoft

There are two problems with this schema: 1. The schema needs a name. Otherwise, it cannot be loaded by the schema editor, e.g., <Schema name="FoodMart"> 2. 'Store Costs' is used in the CalculatedMember, but not defined as a measure. So, add: <Measure name="Store Cost" column="store_cost" aggregator="sum" formatString="#,###.00"/> And after the above changes, the query suggested by Sebastian can be run. If you want to fix the original query, change the ‘descendants’ to ‘children’, i.e., SELECT {[Measures].[unit Sales], [Measures].[store Sales]} ON COLUMNS, {[Time].[1997].[Q1].children} ON ROWS FROM [sales] WHERE [Gender].[F]

If you are familiar with Eclipse, you may start by using the two Eclipse project files - .project and .classpath, located in the jasperserver directory to import the project called 'jasperserver'. Jenngang JasperSoft

Yes, you still need settings.xml, but in case you have the element <offline>true</offline> defined in the file, remove the element or change the value to false. Jenngang JasperSoft

From the build outputs, looks like you are building in the ‘offline’ mode which prevents you from getting needed files from online sources. So, either change <offline>true</offline> to false in your settings.xml, and/or don’t use the offline (–o) option at the command line, and try the build again. Also, if you are building this version of JasperServer for the first time, it’s a good idea to remove the existing directories/files under Maven's .m2repository directory in case the new version has new dependencies that conflict with the existing ones. Jenngang JasperSoft

After trying Maven version: 2.0.7, it doesn't seem to be the problem. What exception did you get when building with Maven version: 2.0.7? I don't find the attachment you mentioned. Jenngang JasperSoft

Regarding the Maven exception, try Maven version: 2.0.4 if that is not the one you are using. Jenngang JasperSoft

Since the totals are pre-defined, it is possible to display a total that does not match the sum when a user omits a sub-category shown in your earlier example. Like the underlining MDX, the GUI does not detect such a discrepancy. This would be a good usability enhancement. For now, the WITH construct can be used to ensure that the sum matches the sub-categories. Jenngang JasperSoft

I am not sure I understand the question precisely. However, since the 'with' construct used in the earlier example is a standard MDX language construct, and as long as the Microsoft Analysis Services interprets a query according to the MDX language definition, it should work. Jenngang JasperSoft

This can be done using the 'with' construct. Try this: with member [Product].[FoodAndDrink] as '([Product].[All Products].[Food] + [Product].[All Products].[Drink])' select {[Measures].[unit Sales]} ON COLUMNS, {[Product].[FoodAndDrink], [Product].[All Products].[Drink], [Product].[All Products].[Food]} ON ROWS from [sales] Jenngang JasperSoft

Please make sure you have the following database creation and jdbc connection settings: - create database with the utf8 characterset option, e.g., 'create database foodmart_cn character set utf8;' - add encoding options to jdbc connection string, e.g., 'jdbc:mysql://localhost:3306/foodmart_cn? useUnicode=true&characterEncoding=UTF-8' Jenngang JasperSoft

I noticed that the encoding used in the schema is GBK, which may be the problem, since Jasperserver supports UTF-8. Jenngang JasperSoft

Please see a similar posting below for a resolution to the #{${... problem. http://www.jasperforge.org/index.php?option=com_joomlaboard&Itemid=215&func=view&id=28367&catid=10&limit=6&limitstart=0 Jenngang JasperSoft

The next release should be around mid-August. Jenngang JasperSoft

#{${requestScope.name}/table}" is the result of embedding JSP expression ${} inside the JPivot expression #{}, specifically in viewOlap.jsp. While the combined expression works in earlier versions of Tomcat, it starts to fail in Tomcat 6. We are considering changing the JPivot expression to #() to get around the problem. If everything goes well, the fix will be included in the next release. Jenngang JasperSoft