|
From: Jean-Pierre <jp...@jp...> - 2003-07-29 20:33:46
|
Rajeev, >>> One more thing. There is no need to comment out the log4j configuration listener for spring samples running under JBOSS. Just use the attached log4j.properties file. I tested your log4j file, but it's no miracle. It is carefully written to well start. Unfortunately, the issue rests when undeploying the application: all JBoss logging are definitively stopped. The server itself can go wrong in this case, but it's not the case with your log4j file. It seems it's the best possible, but I believe like others that with JBoss the logging is better set in JBoss configuration files. So I will provide your file but let the note for commenting out the listener. >>> I actually used the jboss supplied hsqldb-ds.xml file instead of hsql-petclinic-ds.xml. I modified the petclinic build.properties to use the port 1701 for hsql, and the jboss-web.xml to use the "java:/DefaultDS" as the jndi name. This eliminates the step of having to copy a separate hsql-petclinic-ds.xml file in the Jboss deploy dir. The petclinic application works fine with this setting. However, I am still getting the JBOSS "MessageCache" error. Yes, your proposal simplifies the installation by the use of DefaultDS. Just as you made, the port must be set to 1701 in build.properties. I will make changes. For the "MessageCache" error, we will certainly have to live with for the 0.9.1. I have no more time to fix in time. Regards, Jean-Pierre |