We have a recursive macro in one of our velocity templates and keep seeing
the below error:
VM #parseMenuEntry: error : too few arguments to macro. Wanted 9 got 0
VM #dropDownList: error : too few arguments to macro. Wanted 1 got 0
VM #portalLayout: error : too few arguments to macro. Wanted 2 got 0
Each of these velocity templates use a recursive velocimacro. They do work
correctly in the macro, but there doesn't seem to be a way of eliminating
the error message from the the log output (we are using Log4J as our
Logger)
Doing some cursory google searches, I get a couple references to the
following velocity bug:
http://issues.apache.org/bugzilla/show_bug.cgi?id=13623
This bug is still marked as NEW in the bugzilla database and was created in
October of 2002. This message does not look to be fixed anytime soon. I
have also tried the latest velocity available from
http://jakarta.apache.org, version 1.3.1, and the message is still being
echoed.
Does anybody have any insights as to how we can keep this message from
polluting the log over time? The solution I have read on the velocity
mailing lists is to migrate the recursive logic to a java class, and use
the class on the velocity context to do the recursive processing instead of
the macro itself. This solution will not be the easiest to replace in
code, since some of these velocity templates are being called from other
velocity templates.
---------------------------------------------------------------------
To unsubscribe, e-mail: velocity-user-unsubscribe@jakarta.apache.org
For additional commands, e-mail: velocity-user-help@jakarta.apache.org
|