Run-dry statements; database connection pool; reportConfig; JNDI; Tomcat; MyEclipse
The reason why the title of this article Use "by hand" the word is to prevailing on the network using "Run Report ForEclipse statements Chajian dry" integrated distinguishable can state, I search the web for nearly a day, but could not find Run Dry Run training tutorial mentioned dry Eclipse plug-in, plug and just give up the dream of integration, decided to study under the Dry Run training course, to a manual integration. Never mind, still not bad, of a morning, has finally successfully built a report into MyEclipse Run dry environment, with up fairly secure.
I have the MyEclipse 6.6 release, Run Dry statements 4.0, Tomcat is the 6.0 version, JDK 1.6 version.
The first step, open the MyEclipse, then create a new WEB Project, project name tentatively myeclipse_runqian.
The second step, and then open the Run Dry Report Designer, click menu "of local application à à released into the project" in the pop-up "integrated reporting capabilities in project" window, enter the WEB project were WebRoot directory path and Run dry application protocol report file path; If you do not "publish semantic layer file", then deselect the "semantic layer also published document" radio button. Then click "OK" button. As shown below:
It is not a pure manual configuration, if you Run Dry statements very familiar directory structure, you can copy files manually configure the pure form, but for beginners, as is prone to error, so here are borrowed Run Dry release of Report Designer integration, we can say more with less.
The third step is to refresh WEB project in MyEclipse, you will find a lot of work has been integrated Run Dry statements related documents, as shown below:
Newly integrated file may error when WEB.xml common mistake is caused because the following set as follows:
<taglib> <taglib-uri>/WEB-INF/runqianReport4.tld</taglib-uri> <taglib-location>/WEB-INF/runqianReport4.tld</taglib-location> </taglib>
This may be caused because versions, I amended the following error would not have had, as follows:
<jsp-config> <taglib> <taglib-uri>/WEB-INF/runqianReport4.tld</taglib-uri> <taglib-location>/WEB-INF/runqianReport4.tld</taglib-location> </taglib> </jsp-config>
The fourth step is to open reportConfig.xml documents for more detailed configuration.
<!- Report file directory, if there are no special circumstances , Proposed here, of course, you can also modify the path for the other . --> <config> <name>reportFileHome</name> <value>/reportFiles</value> </config> <!- Semantic layer file configuration, if you do not intend to publish the semantic layer file integration , You can here delete Value --> <config> <name>semanticsFile</name> <value></value> </config> <!- Here is the data source configuration, no detailed instructions here , See my related articles . --> <config> <name>JNDIPrefix</name> <value>java:comp/env</value> </config> <config> <name>dataSource</name> <value>jdbc/test,oracle;exercise,sqlsvr,1,iso8859-1,GBK,0</value> </config>
[2010-09-09] small North