This should be fixed in 2.0.2: http://issues.appfuse.org/browse/APF-597
On Mon, Mar 31, 2008 at 1:28 AM, Kai Moritz <[EMAIL PROTECTED]> wrote: > Hi Folks, > > I had troubles running my packed Appfuse-Application on my Tomcat-Server. > As it turned out, velocity was not able to create its logfile in the > "current" > directory through the avalon logkit. > After an hour of painfull work, I found out, how I have to configure velocity > through its properties file, so that it uses the existing logging-framework. > > As I think, that other peopel might stumble accross this problem as well, I > would like to share my results. Besides, I'm wondering, if this might be an > appropriate fine-tuning for the appfuse framework. Because, as far as I'm > concerned, it does not fit into the picture, that velocity is the only > library, which always creates its own standalone logging-file in the current > directory (which might be anywhere). > > Here is my solution: > Create a velocity.properties file at src/main/resources/velocity.properties > and put the following inside: > ------------------------------ > > runtime.log.logsystem.class=org.apache.velocity.runtime.log.SimpleLog4JLogSystem > > runtime.log.logsystem.log4j.category=org.apache.velocity.runtime.log.SimpleLog4JLogSystem > ------------------------------ > > See > > http://velocity.apache.org/engine/devel/developer-guide.html#configuring_logging > http://minaret.biz/tips/tomcatLogging.html#velocity > > I think, this should be added to the tutorials section of the webpage at > least. > > Greetings kai > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] > > --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]