Overview

When a space is started GigaSpaces loading its configuration. The configuration can be stored within space configuration file located at <GigaSpaces Root>\config folder or as part of a space schema configuration file that can be shared across different spaces. See the space configuration search path below:

1. Since the <GigaSpaces Root> folder is first in order in the classpath, before the JSpaces.jar, it will look for the schema file at the following path:
   <GigaSpaces Root>/config/schemas/default-space-schema.xml.
2. Next it will look in the JSpaces.jar, in the same path: (/config/schemas/default-space-schema.xml).
3. Then, if the file was not yet found, it will load the default space schema file from the JSpaces.jar (/config/schemas/default-space-schema.xml).
   If it has a space configuration file, and a schema is defined, the configuration file will be used and not the schema file.
   If the space config does not exist and a schema is defined, the schema file will be used as the template for space creation and its space name will be used as well. In that case (when no space config file existed before space creation), GigaSpaces will not create the space configuration files, but just update the <schema> tag in the relevant space block in the container configuration file.

Container file is created only if there is more than one space created for a running container. In this case the Container file will include the spaces list.