Application Configuration File

The following is an example of a generated configuration file.

<?xml version="1.0" encoding="utf-8" ?>
<configuration>
  <configSections>
    <section name="joob"
             type="JadeSoftware.Joob.Configuration.JoobConfigurationSection,
             JadeSoftware.Joob" />
  </configSections>

  <connectionStrings>
    <add name="myDefault" providerName="JadeSoftware.Joob.JadeConnection"
         connectionString="DataSource=C:/Jade7009/system/;
                           ConfigFile=C:/Jade7009/system/jade.ini;
                           SingleUser=False;
                           Schema=BankingViewSchema;
                           Application=DotNetConnection; 
                           IntegratedSecurity=true"></add>
  </connectionStrings>

  <joob defaultConnection="myDefault">
    <installation directory="C:\Jade7009\bin" />
  </joob>

  <startup>
    <supportedRuntime version="v4.0" sku=".NETFramework,Version=v4.0"/>
  </startup>
</configuration>

Within the <configSections> element there is a joob section, which defines the JADE configuration and is required if you intend using JADE configuration parameters. Within the joob section are a number of options that enable you to customize your application.

In the <connectionStrings> section, specify the JADE database to which the connection is to be established. The <add> sub‑element has a connectionStrings attribute, which contains a series of comma‑separated values that define connection attributes for the JADE database.

Specifying an application causes the JADE initialize or finalize methods defined on that application to be invoked. (The default application, RootSchemaApp, does not have initialize or finalize methods defined.)

Specifying an application causes the JADE initialize and finalize methods defined on that application to be invoked. (The default application, RootSchemaApp, does not have initialize or finalize methods defined.)