Tauren Mills wrote: > If I was to allow the client to customize and upload new CSS files, > how would you suggest this be done? Where would the CSS files be > saved and how would the app know where to look for them? How would > the override the CSS files that are within the WAR file? > > Also, as far as static content management goes, I'm thinking of > putting all the static stuff into the properties files and using > labels for it. Thus creating a very simple and cheap CMS. Then it > would be simply a matter of editing the properties files and uploading > them. But again, how would that work? What would I do so that the > app would read the uploaded files instead of the ones in the WAR?
It's easy enough to provide a custom resource locator for strings or whatever. You can pull these out of a database, or properties files, or whatever else floats your boat. For CSS, you could provide FTP access to a folder with CSS files in. You can then have a configuration screen in the app which picks which file to use (possibly with a testing mode). You then add the CSS as a HeaderContributor resource, pointing at the location on disk, allowing Wicket to serve it. That way, the CSS can be outside your WAR file. Sounds to me like you want to package the thing as a WAR file to discourage tinkering with the internals. Regards, Al -- Alastair Maw Wicket-biased blog at http://herebebeasties.com ------------------------------------------------------------------------- This SF.net email is sponsored by DB2 Express Download DB2 Express C - the FREE version of DB2 express and take control of your XML. No limits. Just data. Click to get it now. http://sourceforge.net/powerbar/db2/ _______________________________________________ Wicket-user mailing list Wicket-user@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wicket-user
