You may be wondering why the tutorial works with only a few properties, and why we have our own versions of the configuration-property files. The reason is that Jetspeed does not have a standard way to deploy portlet applications, thus with version 1.x we have to merge property files in order for a portal application to override and define its own configuration properties, and also to avoid editing the Jetspeed property files everytime they are modified in the CVS.
The Jetspeed Plugin file in the JPortal source is capable of doing just that. It merges the JPortal Tutorial configuration files shown below on the left into the master Jetspeed resource files on the right:
|Tutorial Configuration (Merge) File||Jetspeed Configuration (Master) File|
The merge program is included in the Jetspeed Plugin. The general rules for merging properties are:
** with the exception of the include directive and module.properties property, which are added since there can be multiple include directives or module.packages properties.
There are many properties in the default Jetspeed configuration that arent used by many sites. For instance, the RSS and OCS support, which requires background threads to be running, can automatically be removed by merging them out of the master properties file. This is accomplished using a remove directive and prefix strings in your merge property file:
-contentfeeds. -#contentfeeds. -daemon. -services.DaemonFactory -content. -#content.
Any line that begins with a dash "-" will instruct the property merger to remove a property starting with the given prefix string immediately following the dash. The prefix-string can include comments (or all comments).