
|
If you were logged in you would be able to see more operations.
|
|
|
WebWork
Created: 11/Aug/04 10:45 PM
Updated: 19/Oct/04 11:06 AM
|
|
| Component/s: |
Views
|
| Affects Version/s: |
2.2
|
| Fix Version/s: |
2.1.5
|
|
|
I have been having problems getting my velocity macros to autoreload. My velocity.properties file looks like:
wwfile.resource.loader.cache = false
velocimacro.library = macros.vm
velocimacro.library.autoreload = true
When looking through the VelocityManager.java file, I found that I would not be able to get the wwfile.resource.loader to ever set cache to false (so that it will allow autoreload)
The problem is that the applyDefaultConfiguration method is hard-coding the cache to 'true'.
Could I suggest that the VelocityManager.loadConfiguration method be changed so that the defaults are loaded first, and then users can override via the velocity.properties file.
Currently the user settings are read in from velocity.properties, but they get overridden by the system defaults.
|
|
Description
|
I have been having problems getting my velocity macros to autoreload. My velocity.properties file looks like:
wwfile.resource.loader.cache = false
velocimacro.library = macros.vm
velocimacro.library.autoreload = true
When looking through the VelocityManager.java file, I found that I would not be able to get the wwfile.resource.loader to ever set cache to false (so that it will allow autoreload)
The problem is that the applyDefaultConfiguration method is hard-coding the cache to 'true'.
Could I suggest that the VelocityManager.loadConfiguration method be changed so that the defaults are loaded first, and then users can override via the velocity.properties file.
Currently the user settings are read in from velocity.properties, but they get overridden by the system defaults. |
Show » |
|