Announcement Announcement Module
No announcement yet.
Externalising resources Page Title Module
Move Remove Collapse
Conversation Detail Module
  • Filter
  • Time
  • Show
Clear All
new posts

  • Externalising resources

    We have an application where the look and feel (images, style sheets and text) varies between implementations, e.g. if we ship to Fred Blogs Loans limited the app gets branded with that companies look and feel.

    Using the traditional way (we use RAD) text is in properties files, and images and style sheets are in theme directories within the source structure of the project. We just use RAD to export and EAR file and ship that.

    Using this method means we need to change source code (e.g. text) and re-ship the EAR to give a new look and feel.

    I've looked at storing the text, images and style sheets in database tables, which means the look and feel is data driven rather than effectively hard coded and buried with the EAR. Are there any alternative or better ways of doing this ?