Not quite sure what you mean by a debugger. Do you mean a mechanism to see problems in a Velocity page?
For parse errors, Velocity 1.5 throws an Exception providing the line number, column number, and template name of the error. The Click framework uses this info to do a nice job of highlighting the specific error. http://click.sourceforge.net/ In addition, there's a new event handler in Velocity 1.5 that will catch and return all invalid references, perhaps this is of help. WILL On 1/24/07, Bruno GUEDES <[EMAIL PROTECTED]> wrote:
Hi everybody, Have you plan to create an Debugger, for exmample an Eclipse Debugger ;-) ??? Well, if possible, can I ask with somebody of the velocity task, about it ??? Have a nice day ... Sincerely Bruno --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
-- Forio Business Simulations Will Glass-Husain [EMAIL PROTECTED] www.forio.com --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
