Hello, this is my first post on the list...
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 below.
1) Servlet get a reference to a
Will Glass-Husain [EMAIL PROTECTED] wrote:
Doesn't quite work that easily.
The problem is that if #directive is not an actual macro, than
\#directive
is shown verbatim. You only should escape when the same code is legit in
both the source and the generated Velocity. This can be a
Doesn't quite work that easily.
The problem is that if #directive is not an actual macro,
than \#directive
is shown verbatim. You only should escape when the same
code is legit in
both the source and the generated Velocity. This can be a
little confusing.
I know there is no
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
In my effort to find a solution to the problem I mentioned in another post I'm
trying to setup minimal Velocity logging...
There must be something wrong with my setup (or with me :-)).
1) loadConfiguration is called (see above for source code) but NOT under cactus
(it's normal I should find a
I am actively and successfully using Struts 1.2.x with VelocityTools 1.2dev
and Velocity 1.4.
Admittedly I haven't been using the ValidatorTool (only use server side
validation) but I still took some time to upgrade it so it should work fine
for Struts 1.2.x now (the app5 velstruts example has
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
Yes. It's confusing. But I'd vote against changing this (for the 1.x
series) or all
my app-generating templates will break.
WILL
- Original Message -
From: Gonzalo Diethelm [EMAIL PROTECTED]
To: 'Velocity Users List' velocity-user@jakarta.apache.org
Sent: Friday, February 25, 2005
agreed. this is not my preferred escaping system either, but we can't
just go changing it now. i can't think of any way to make such a
change backwards compatible.
the best that could be done (if someone is interested in doing it) in
1.x, would be to make escaping behavior configurable via a
10 matches
Mail list logo
