Poor general OLAP solution III-July performance Layer

July is the taglib of Mondrian's performance layer, which maintains a good development progress.
I have never used it for a long time. I forgot about it and wrote down my little experiences.

1. Localization
1.1 search for all resources. properties files and convert them to resources_zh.properties files.
1.2 native2ascii resources_zh.properties
1.3 search for all XML files under the WEB-INF/jpivot and convert them to xxx_zh.xml

2. Architecture
July's architecture seems an alternative, but it is actually a smart choice.

2.1 rendering OLAP reports using XML/XSLT
July uses WCF (Web Component Framework) to render Web UI components based on XML/XSLT. This makes it very different. However, OLAP reports, which are complex but regular, are most suitable for rendering using XSLT. Although programmers and editors do not like this kind of LISP Language in Martin flower, transform engine is indeed comparable to template engine (velocity, freemarker) at this time) more efficiently process the display of OLAP reports and their navigation systems.

2.2 fully Based on JSP + taglib
Another thing that July may not be used to is that it is completely based on taglib rather than the familiar MVC pattern. However, without tablib, any MVC framework will make it out of universality and cannot afford the unique performance Layer of mondrain. Moreover, MVC does not necessarily need those frameworks (as described later)

2.3 typical processes and models:

Open the sample that comes with July and view the index. jsp file. The typical process is as follows:

1. the user sends testpage. jsp? Query = modrain request

2, testpage. jsp on the <WCF: Include> according to the query parameters, match/WEB-INF/query/Under the modrain. jsp to get data

3. <JP: mondrianquery id = "query01"> query data on modrain. jsp and put it in the query01 variable.

4, testpage. <JP: Table id = "table01" query = "# {query01}"/> based on the results of query01 (domain data) prepare the data required to display the OLAP table (display data)

5, testpage. on JSP <WCF: render ref = "table01" partition uri = "/WEB-INF/jder/table/mdxtable. XSL "/> uses XSL to render the OLAP table based on the results of table01.

6. Loop step 4 and Step 5. Use the <JP: navigator> tag to prepare the navigator and chart data and then use <WCF> to render the chart and navigation system.

Throughout the process, testpage in step 1 acts as the Controller to call the model layer in step 2, and then executes the transform engine two-step rendering mode described by Martin flower in step 4 and 5 ----First, convert the domain data (such as some java beans) to the formatted data that needs to be displayed (such as a piece of XML), and then use XSL to render it as the final form.

Related Articles:
General OLAP solutions for the poor I-Sequence
Poor general OLAP solutions I-Mondrian Engine
General OLAP solution III for the poor-July performance Layer