I'm using the default Jetty for which the logs are created. The cocoon logs, in WEB-INF/logs are not created. If the pre-created log files are deleted from WEB-INF/logs then they are not recreated at all. This makes me think that it may be some config parameter that may be fouling it up! -Yatin
Marco Rolappe wrote:
please have a look at tomcat's logs. maybe there's a premature failure preventing the logger from doing its job.
-----Ursprüngliche Nachricht----- Von: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] Auftrag von Yatin Shah Gesendet: Freitag, 7. März 2003 06:59 An: [EMAIL PROTECTED] Betreff: Can't enable logging & can't connect to MySQL
I've just downloaded the dev version from cvs(Mar 7 12:05 AM EST) and I can't enable the logging facility.
I've changed WEB-INF/web.xml to set log-level to DEBUG and changed all log-level="ERROR" to log-level="DEBUG" in WEB-INF/logkit.xconf. Is there anything else required to enable the logging facility?
Further, I can't connect to MySQL server from cocoon. I've done it my old environment(cvs version from Oct, 2002) by setting the load-class parm to com.mysql.jdbc.Driver along with org.hsqldb.jdbcDriver in web.xml and setting the datasources jdbc entry in the cocoon.xconf. [I have the correct jar in WEB-INF/lib and tools/jetty/lib - mysql-connector-java-3.0.6-stable-bin.jar; My servlet, running in the same Jetty container connects to database without any problems]
Any suggestions on how to resolve this?
