Hi Shinobu,
Shinobu Kawai wrote
Yeah, I know. I sometimes forget to mention that I actually did attempt to solve the problem before asking a question :)I already looked at the configuration
options and none of them solve this problem (atleast, not to my knowledge).
Oooh, you should have mentioned that on your first post. :)
Yeah. So I noticed :) I already guessed it from the description, but there was a small hope that maybe the macro loaded from the global macro could actually invoke the local... and making the scope local would make sure the new #x overwrote the old #x .. unfortunately even though it might have, I could never reach it, so it had no use...The problem is a bit with the call-back mechanism. If I set the property
velocimacro.permissions.allow.inline.local.scope on true the behaviour
changes, it never loads it at all...
Makes sense, because the local macros won't be visible to invokeX.html.
Try setting velocimacro.permissions.allow.inline.to.replace.global toYeah, that worked! but I'm not entirely sure whether I'm happy about turning cache off.... after all, cache is kinda handy in a production environment. In theory I could of course store this macro in a separate directory, pointing another resource loader with cache off towards.. the loading it with a #parse statement in the main page... but that would make it just that bit more complicated.
true. This will let each call overwrite the previous macro
definition. You'll also have to turn caching off.
The funky thing is that if I turn cache on and change global.html (see previous posting) to this:
#macro(invokeX)
Global: #x() <br />
#parse("invokeX.html")
#endThe global macro invokes the correct #x on te correct page, but the invokeX.html doesn't. I don't know how velocity's cache works but I don't understand why #x is bound to invokeX. If it wasn't this should work properly, right?
Thanks, Vincent
-- No virus found in this outgoing message. Checked by AVG Anti-Virus. Version: 7.0.308 / Virus Database: 266.6.0 - Release Date: 2-3-2005
--------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
