General OLAP solution III for the poor-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. To find all resources. properties files in Chinese, to resources_zh.properties file 1.1 native2ascii resources_zh.properties 1.2 to find all xml files in WEB-INF/jces, to xxx_zh.xml in Chinese
2. The July architecture seems to be an alternative, but it is actually a smart choice.
2.1 Using XML/XSLT to render OLAP report July using 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 completely based on JSP + TagLib j.pdf another thing that may be undesirable 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 process and model:
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.