data), or the form configuration files (
*). Wildcards allow you to setup Orbeon Forms to use different persistence providers for different app, form, and resource type combinations.
orbeonand form name
oracleis predefined, the following configuration will do just that:
hrapp in one Oracle database schema and everything related to another
financeapp in another Oracle database schema. For more on this, see how to setup the persistence layer for multiple schemas.
uriproperty specifies the location, via HTTP, of the provider implementation.
activeproperty specifies whether the provider is active.
permissionsproperty specifies whether user/group permissions are supported.
true, Form Runner assumes that permissions are supported by the provider implementation.
versioningproperty specifies whether versioning is supported.
true, Form Runner assumes that versioning is supported by the provider implementation.
data-format-versionproperty specifies which data format version is in the database.
2019.1.0[SINCE Orbeon Forms 2019.1]
4.0.0for backward compatibility.
oxf.fr.detail.new.service.enableproperty always assumes data in
4.0.0format even if the property above is set to a different value.
true, to instruct Orbeon Forms to escape all non-ASCII characters in form data before they are sent to the database.
éin a field, and that you have this property enabled, then the form data will contain
é, which is the escaped version of
é, however, if that field is indexed (because you've enabled Show on Summary page or Show in search in the Control Settings for that field), then the character
éwill be stored in the index table, which might be a problem if your database encoding cannot accommodate the storage of this character.
footo go to
barto go to