On 25 Feb 2005 at 10:33, Nathan Bubna wrote:
i don't really know anything about Cactus, but this code snippet
hardly seems representative of a sensible way to test a servlet.
surely they must have a better setup than this? or am i just getting
the wrong impression because you've posted
On 25 Feb 2005 at 10:33, Nathan Bubna wrote:
anyway, the VelocityViewServlet requires a good bit more than just the
handleRequest() method to run. first it will need to be init'ed
(going thru init(), initToolbox(), initVelocity() and
loadConfiguration()), then it calls createContext() to
On Sat, 26 Feb 2005 10:34:21 +0100, [EMAIL PROTECTED]
[EMAIL PROTECTED] wrote:
On 25 Feb 2005 at 10:33, Nathan Bubna wrote:
anyway, the VelocityViewServlet requires a good bit more than just the
handleRequest() method to run. first it will need to be init'ed
(going thru init(),
Hi Christophe,
Hello, this is my first post on the list...
Welcome to the gang! :)
I have a problem using Cactus test suites with my servlet (which is
inherited from VelocityViewServlet) and I wonder if it could be due to the
way I'm using Velocity API.
I've summarized some informations
Hello
I'm using the latest stable releases of Velocity and Velocitools.
To avoid being to verbose on cutting pasting tons of source code here, this
is just the way the servlet is invoked under cactus :
public void setupServletAndRun() throws Exception
{
AnaemServlet servlet = new
i don't really know anything about Cactus, but this code snippet
hardly seems representative of a sensible way to test a servlet.
surely they must have a better setup than this? or am i just getting
the wrong impression because you've posted so little code?
anyway, the VelocityViewServlet
