velocity-user mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Geir Magnusson Jr." <>
Subject Re: Parsing error... ?#~
Date Thu, 12 Jul 2001 03:59:05 GMT
Dan Finkelstein wrote:
> I'm not sure what to try next so I thought I'd bounce this weirdness off
> you guys...

Oh no... I hate wierdness.

> Our system goes through a bunch of velocity templates and processes
> them.  When it gets to one, it generates this error:
>    7 of 21: C:/projects/gusa/builds/common/b0/templates/Wrapup.html
> Velocity Parsing error:
>          Message...Encountered "/" at line 67, column 25.
> Was expecting one of:


> so I think the line numbers are off.  Anyway, this file does use a macro,
> #OutputParagraphs(string), which is stored in a library file and accessed
> as follows from the first line of the template:
>         #parse ("build/common/b0/templates/include/preprocessorLibrary.vm")

Ah ha.
> If I paste in the contents of this library into the template, replacing the
> #parse line, velocity processes the file without an error.  I don't know
> what the differences are between calling a macro "in-line" vs. through a
> parsed file...

You can't parse in a VM definition like this.  Why?  Because #parse() is
a run-time thing, and the binding of VMs in the template happens at
parse time.  So the VMs have to be registered before parsing the
template. (It's something I'm working on...).
> The final observation I have is that in our system we have something like a
> "make", where only changed files are processed by velocity.  When we do a
> "make all" this error doesn't occur.  It only occurs, it we change the
> template file (that being one only file needing to process) and then run
> "make".  It's as thought something has "primed" velocity in the "make all"
> situation...

This is consistant with the above #parse() problem.

Solution?  Well, looking at it, it seems that the preprocessorLibrary.vm
isn't local to that template.  So you can simply have velocity read it
and register the VMs at startup using the configuration key

velocimacro.library = <library1>,<library2>,<library3>...

in your (or however you configure the runtime...)

(so yes, you can specify multiple libraries to be read in...)

Does that help?


Geir Magnusson Jr.                 
System and Software Consulting
Developing for the web?  See
You have a genius for suggesting things I've come a cropper with!

View raw message