12.4. Configuration Tips and Tricks
12.4.1. Defining Default Value for a Property
When you define a property, you can provide a default value for it. To define this default value, append the default value to the property name, separated by a colon (:). For example:
${server.port:8080}12.4.2. Defining Environment Properties
12.4.2.1. Environment Properties as Component Properties
You can define properties as component properties. This way of defining properties is not dynamic, but you can override each property defined here, by properties defined in a prioritized scope.
<sy:switchyard ...>
<sca:composite ...>
<sca:component ...>
...
<sca:property value="test" name="MY_PROPERTY"/>
</sca:component>
<sca:service...>
...
</sca:service>
<sca:reference ...>
...
</sca:reference>
</sca:composite>
...
</sy:switchyard>
12.4.2.2. Environment Properties as Composite Properties
You can define properties as composite properties. This way of defining properties is not dynamic, but you can override every property defined here, by properties defined in a prioritized scope.
<sy:switchyard ...>
<sca:composite ...>
<sca:component ...>
...
</sca:component>
<sca:service...>
...
</sca:service>
<sca:reference ...>
<sca:interface.java .../>
<file:binding.file name="FileBinding">
<file:directory>/tmp</file:directory>
<file:fileName>${MY_FILENAME}</file:fileName>
<file:produce/>
</file:binding.file>
</sca:reference>
<sca:property value="test.txt" name="MY_FILENAME"/>
</sca:composite>
...
</sy:switchyard>
12.4.2.3. Environment Properties as Domain Properties
You can define properties as composite properties. This way of defining properties is not dynamic, but you can override each property defined here, by properties defined in a prioritized scope.
<sy:switchyard ...>
<sca:composite ...>
<sca:component ...>
...
</sca:component>
<sca:service...>
...
</sca:service>
<sca:reference ...>
...
</sca:reference>
</sca:composite>
...
<sca:domain>
<sca:property value="test.txt" name="MY_FILENAME"/>
</sca:domain>
</sy:switchyard>
12.4.2.4. Environment Properties as OS Environment Properties
You can load properties from OS environment properties. Every environment property is accessible by prefixing it with env. For example, in bash, you can use a property defined as
export MY_PROPERTY=test, in your SwitchYard application as shown below:
<ftp:binding.sftp>
<ftp:host>${env.MY_PROPERTY}</ftp:host>
....
</ftp:binding.sftp>
12.4.2.5. Environment Properties as Application Server Properties from AS Configuration
Application server has the ability to define properties directly in its configuration either by file or with the console. This configuration is dynamically updated and persisted.
Add the configuration to the server definition as shown below:
<server name="xyz.home" xmlns="urn:jboss:domain:1.0">
<extensions>
<extension module="org.jboss.as.clustering.infinispan"/>
<extension module="org.jboss.as.clustering.jgroups"/>
<extension module="org.jboss.as.connector"/>
....
</extensions>
<system-properties>
<property name="MY_PROPERTY" value="test"/>
</system-properties>
This property is used in your SwitchYard application as:
<ftp:binding.sftp>
<ftp:host>${MY_PROPERTY}</ftp:host>
....
</ftp:binding.sftp>
12.4.2.6. Environment Properties as Application Server Properties from File
You can pass a properties file as an argument to JBoss Application Server (AS) startup script to load all the properties in the file and make them accessible. You can start the AS as shown below:
$./standalone.sh -P file:///data/production.properties
Here are some alternatives:
- -P=<url>: Load system properties from the given URL
- -P<url>: Load system properties from the given URL
- --properties=<url>: Load system properties from the given URL
In your SwitchYard application, you can use these properties as:
<ftp:binding.sftp>
<ftp:host>${env.MY_PROPERTY}</ftp:host>
....
</ftp:binding.sftp>
12.4.3. Loading Properties for Test
In tests, you can add and resolve properties at the top level. The PropertyMixIn eases working with properties:
private PropertyMixIn pmi;
...
pmi.set("test.property.name", "test");
pmi.set("test.property.name", Integer.valueOf(100));
...
pmi.get("test.property.name");
...
In case you need access to the PropertyResolver for tests, where a MixIn is not applicable, you can use TestPropertyResolver.INSTANCE and avoid setting command line parameters as shown below:
TestPropertyResolver.INSTANCE.getMap().put("name","value");
