re:"no report config file" error message
We can't get any useful information for the error message, in fact, the reason is some detail neglected when the config file is edited, and mistakes were made next, let's see the right config file codes.
Step 1: The details in reportConfig.xml that should be noticed
Step2: you should note that the datasource name in the config file should be in accordance with the one that connected in the report, or the no config file error will be reported.
the configuration information of the datasource in reportConfig.xml is as follows:
<config>
<name>dataSource</name>
<value>demo,hsql,gbk</value>
</config>
Step3: next let's see the servelet configuration about RAQ Report in web.xml.
In the web.xml file, the servlet and taglib use in report system are configured, if the Other servlets and filters are configured in the project, you should make sure that it will not have any effect on the servlet of the report, otherwise the report will not run properly.
Step4: check the config file of the database connection pool, generally with the same name as the application folder, here we named it demo.xml (the database connection configuration of weblogic and websphere server is in a wizard style, please refer to the J2EE deployment documentation for more detail):
Take tomcat as an example, the configuration of database connection pool of tomcat5.5 or earlier version is as shown below:
<Context docBase="demo" path="/demo" debug="0" privileged="true">
<Resource name="demo" auth="Container" type="javax.sql.DataSource"/>
<ResourceParams name="demo">
¡*¡* The configuration of database connection pool changed for version of the application server after tomcat5.5-tomcat6.0, as shown below:
<Context docBase="demo" path="/demo" debug="0" privileged="true">
<Resource name="demo" auth="Container" type="javax.sql.DataSource" factory="org.apache.commons.dbcp.BasicDataSourceFactory" maxActive="10"
maxIdle="30"
maxWait="10000"
username="sa"
password=""
driverClassName="org.hsqldb.jdbcDriver"
url="jdbc:hsqldb:hsql://localhost/runqianDB"
/>
</Context>
<ResourceParams name="demo">
Step5: there's one more thing you should notice, after modifying the config file, you need to clear the server cache and restart service and reload the config file.
To sum up, it's not that hard to handle the "no report config file" error, just make sure the code and position in the cofig file are right, when the error comes out, check the file according to the items mentioned above, and problem will be solved.
This post is from freezea's blog. You are welcomed cc it anywhere, and please indicate the source.
If you would like to read more articles about reporting tool, you are also welcome to refer to my blog.
