Since we are not using velocity we were able to remove the velocity
libraries, and this issue was resolved.
-Original Message-
From: Christopher Schultz [mailto:ch...@christopherschultz.net]
Sent: Wednesday, March 27, 2013 2:38 PM
To: Tomcat Users List
Subject: Re: Velocity Logging
I am using Wicket 1.4.22 with Tomcat 7.0.37 and JDK 1.6.0_33. The recent
upgrade to Tomcat created an issue where the cannot
be undeployed unless the app is shut down due to the Wicket dependency
velocity logging in use (1.4).
We are running a web application under tomcat using the wicket
On Wed, Mar 27, 2013 at 4:16 PM, Bruce Pease bpe...@wth.com wrote:
I am using Wicket 1.4.22 with Tomcat 7.0.37 and JDK 1.6.0_33. The recent
upgrade to Tomcat created an issue where the cannot
be undeployed unless the app is shut down due to the Wicket dependency
velocity logging in use (1.4
dependency velocity logging in use (1.4).
We are running a web application under tomcat using the wicket
framework. A requirement for Wicket is the velocity libraries.
The velocity framework is auto loading and writing to a log in the
conf directory. Since it is in use I am unable to undeploy
