Note, for some people wanting to do something similar - here's what I did to make it work.
1) subclassed HibernateRollerImpl then override the getThemeManager() method (returned my own ThemeManager implementation which is basically just a copy of the ThemeManagerImpl except the getTheme method keeps loading from the disk instead of the private Map). 2) Modified roller-custom.properties and made sure the roller implementation was using my class above. 3) Modified the velocity.properties file and made sure the following properties were set theme.resource.loader.cache=false additionally, changed the classpath resource loader to a FileResourceLoader instead eq. class.resource.loader.description = Velocity Classpath Resource Loader class.resource.loader.class = org.apache.velocity.runtime.resource.loader.FileResourceLoader class.resource.loader.path=C:/build/blogs/trunk/build/roller/WEB-INF/cla sses class.resource.loader.cache=false class.resource.loader.modificationCheckInterval=0 G -----Original Message----- From: James M Snell [mailto:[EMAIL PROTECTED] Sent: Wednesday, April 04, 2007 9:31 AM To: [email protected] Subject: Re: refactoring object model for themes +1. A development mode setting would be very very very helpful :-) - James George Daswani wrote: > It would also be nice if there was an option to disable Theme caching > and velocity macro caching in general - for those people who write > Themes (some of our UI people absolutely hate working with Roller > because of this). > [snip]
