Dear Wiki user, You have subscribed to a wiki page or wiki category on "Lenya Wiki" for change notification.
The following page has been changed by MarkusAngst: http://wiki.apache.org/lenya/LenyaProperties ------------------------------------------------------------------------------ - ==Introduction== + == Introduction == Lenya and your publications can be configured with properties files. This can be useful for setting global, deployment and publication specific parameter values like database usernames and passwords, SMTP server hostnames and the like. - ==Setting properties== + == Setting properties == You can set properties in two different ways: * using Java system properties on the command line * in properties files - ===Properties files=== + === Properties files === Properties files can be found in the following places: * Lenya properties at `$LENYA_HOME/lenya.properties.xml` and $LENYA_HOME/local.lenya.properties.xml * Module properties at `$LENYA_HOME/lenya/modules/<modulename>/lenya.properties.xml` * Publication properties at `$PUB_HOME/lenya.properties.xml` - ===Order of precedence=== + === Order of precedence === Properties with the same name (including prefix) and located in different properties files can override each other. The order of precedence is (lower number wins): 1. Publication @@ -29, +29 @@ Module properties are visible to all publications, regardless of the publication using a particular module or not.[[BR]] System properties should probably override publication properties. At the moment they don't.[[BR]] - ===Name prefixes=== + === Name prefixes === Prpoerty names should use name prefixes to avoid confusion and accidental overriding. The following name prefixes are suggested: * Lenya properties: `lenya.<propertyname>` * Module properties: `<modulename>.<propertyname>` @@ -39, +39 @@ System properties are normally used to override existing Lenya or module properties. Publication properties cannot be overridden by system properties at the moment. - ==Using properties== + == Using properties == The properties are accessible by an input module. They can be used in sitemaps wherever the usage of an input module is appropriate. For example: {{{ <map:pipeline type="..."> --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]