|
Summary: How to specify the container name when starting a space; overwriting default container configuration in runtime.
"." Container NotationThe Space URL uses the following notation to start a space: "/./<Space Name>" When using the space URL the SpaceFinder/CacheFinder will instantiate (create) a space instance named "mySpace" using the default schema configuration. The default schema is set to transient space configuration and it is equivalent to using the following URL: "java://localhost:10098/mySpace_container/mySpace?schema=default".
When a URL is provided without the protocol (java) and host name (localhost), the SpaceFinder/CacheFinder treats "/./mySpace" as java://localhost:10098/mySpace_container/mySpace?schema=default. Overwriting Existing Configuration FilesYou may overwrite the existing default schema configuration files by the creation of a <container-name>-config.xml and <space-name>.xml file. If these files exist they will overwrite the default configuration defined by the schema files. Such overriding will should be used for backward compatibility. In other cases, for backward compatibility, if you have a space configuration file, then the schema will be overridden.
There is no need to have the space configuration files if you have defined the schema name as part of the SpaceFinder/CacheFinder, or if you use Java:// protocol with the ?create option (this uses the default-space-schema.xml file). |
Wiki Content Tree
Your Feedback Needed!
We need your help to improve this wiki site. If you have any suggestions or corrections, write to us at techw@gigaspaces.com. Please provide a link to the wiki page you are referring to.
Add Comment