Recent changes to webwork included the addition of some macros for backwards compatibility. As part of this change, though, I'm seeing problems with configuring other macros. I've been using a velocity.properties file that includes declarations of 2 additional macro files. This has been working for a while. Now, macros defined here don't seem to make their way into webwork, even though my servlet startup log contains the following line:
2003-11-18 11:43:34,449 [INFO] velocity.VelocityManager - Initializing velocity using 'velocity.properties'
I've noticed that the velocityManager class includes the following line in "applyDefaultConfiguration":
p.setProperty("velocimacro.library", "webwork.vm");
I don't know if this is overwriting any other settings or what, but including the line
velocimacro.library=mymacro.vm
doesn't seem to prepare any custom macros for use. I've tried this in both velocity.properties and webwork.properties, to no avail. I have a set of libraries under the "macro" directory of my source directory, and declare them as follows (previously in velocity.properties):
velocimacro.library=macros/mymacrofile1.vm,macros/mymacrofile2.vm
This worked up until the version of webwork I pulled down lsat Friday.
Give it a whirl again Drew. I've pulled the
> p.setProperty("velocimacro.library", "webwork.vm");
which shouldn't have been in there and placed it into velocity.properties. So you're free to use the macros if you like or override them.
M
------------------------------------------------------- This SF.net email is sponsored by: SF.net Giveback Program. Does SourceForge.net help you be more productive? Does it help you create better code? SHARE THE LOVE, and help us help YOU! Click Here: http://sourceforge.net/donate/ _______________________________________________ Opensymphony-webwork mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/opensymphony-webwork
