Alexander Zimmer wrote:
> Hello list,
>
> I am trying to modularize an existing turbine 2.3.2 app. The app should
> be shipped to several customers, each with a distinct layout. But - how?
>
> As far as I can see, the skin mechanism is not enough because I can only
> "skin-ize" images, colors etc. Instead, what I want to do is to
> implement completely different layout sets having customer specific
> appearance beyond just replacing images: e.g. using a table layout for
> one customer and using sophisticated <div> elements for the other.
>
> My first idea was: put each customer layout set in different subdirs of
> the templates/app/* directories, e.g:
I suggest something like this:
/templates/customer1
layouts
screens
...
/templates/customer2
layouts
screens
...
Read the docs about TurbineConfiguration.xml. Add the access to the JNDI
context to the configuration file, for example:
<configuration>
<jndi prefix="java:comp/env"/>
<properties fileName="WEB-INF/conf/Deployment.properties"
optional="true"/>
<properties fileName="WEB-INF/conf/TurbineResources.properties"/>
</configuration>
Now you can add an Environment entry to the context descriptor of your
application server (e.g. Tomcat) like so:
<!-- Customer configuration -->
<Environment
name="services/VelocityService/file/resource/loader/path"
type="java.lang.String"
value="/templates/customer1" />
Note the slashes instead of the dots. You can overwrite any setting of
TurbineResources.properties in this way.
HTH
Bye, Thomas.
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
