Allows to use different annotation based injection and configuration. A space factory bean that creates a space (IJSpace) based on a url and additional settings. The size of the cache. When a space is running in a persistent mode (i.e. using the HibernateDataSource implementation), The initial_load sets the % of the space cache data to be loaded (default is 50%) maximum size. To disable this initial load phase, you should configure the initial_load value to be 0. Sets the url properties. Note, most if not all url level properties can be set using explicit attributes. ". ]]> Sets the properties the IJSpace will be created with (same as parameters). Note, this should not be confused with url-properties. The properties here are the ones referred to as custom properties and allows for example to control the xpath injection to space schema. ". ]]> Sets the parameters the IJSpace will be created with (same as parameters). Note, this should not be confused with url-properties. The properties here are the ones referred to as custom properties and allows for example to control the xpath injection to space schema. ". ]]> Allows to inject a "pure" space filter based on SpaceFilterProviderFactory that accepts an ISpaceFilter implementation. Allows to inject a an annotation adapter based on AnnotationFilterFactoryBean that accepts a pure pojo with annotations marking filter methods. Allows to inject a a method adapter based on MethodFilterFactoryBean that accepts a pure pojo with method marking filter methods. Allows to inject a general implementation of FilterProviderFactory. Reference to the bean. Inject an instance of ReplicationFilterProviderFactory allowing to provide a Space replication filter. Reference to the bean. Simplified option for injecting space replication filter without using the factory. Defines a single document type for the space The url the space will be created with. The schema name associated with the space. The Jini Lookup Service group to find container or space using multicast (jini protocol). Groups are comma separated list. The Jini Lookup locators for the Space. In the form of: host1:port1,host2:port2. The max timeout in milliseconds to find a Container or Space using multicast (jini protocol). Defaults to 6000 (i.e. 6 seconds). When false, optimistic locking is disabled. Default is true. If true - Lease object would not return from the write/writeMultiple operations. Defaults to false. When setting this URL property to true it will allow the space to connect to the Mirror service to push its data and operations for asynchronous persistency. Defaults to false. Indicates that all take/write operations be conducted in FIFO mode. Default is false. Indicates that this space will register for space mode notifications. Default behavior (if the flag was not set) will register to primary backup notification if the space was found using an embedded protocol, and will not register for notification if the space was found using rmi or jini protocols. Allows to provide a Space external data source reference. Should this Space bean control if the cluster member is alive or not. Defaults to true if the Space started is an embedded Space, and false if the it is connected to a remote Space. A gateway factory bean that creates gateway replication targets for a space. A space factory bean that creates a mirror space based on a url and additional settings. The name of the source space that connects to this mirror. The number of partitions the source space has. The number of backups each partition on the source space has. Allows to provide a Space external data source reference. Sets the properties the IJSpace will be created with (same as parameters). Note, this should not be confused with url-properties. The properties here are the ones referred to as custom properties and allows for example to control the xpath injection to space schema. ". ]]> Configures distributed transaction processing configuration for the Mirror component. Sets the timeout (in milliseconds) for distributed transaction partial participants commit. Sets the number of operations to wait until distributed transaction partial participants commit. The url the space will be created with. Allows to provide a Space external data source reference. The url the space will be created with. The default replication filter provider factory allowing to configure an input and output filter of IReplicationFilter. The input replication filter. The output replication filter. A FilterProvider factory that accepts a concrete ISpaceFilter implementation in addition to all the operation codes it will listen to. The operation code the filter will be registered to. Operation code stands for a specfic operation the space will perform, for example, before write. The operation code (number) the filter will be registered to. Operation code stands for a specific operation the space will perform, for example, before write. The operation code (name) the filter will be registered to. Operation code stands for a specific operation the space will perform, for example, before-write. A FilterProvider factory that accepts a Pojo filter with annotation markers as to which filter operation to listen to. The available annotations are the different annotations found within this package with either the Before prefix or the After prefix (for example: BeforeWrite and AfterWrite). Filter lifecycle methods can be marked using OnFilterInit and OnFilterClose annotations. A FilterProvider factory that accepts a Pojo filter with different operation callbacks that are marked using this factory. For each available operation there is an attribute that accepts the method name to be invoked if the operation happened. Not setting a callback means that this filter will not listen to the mentioned operation. For example, if the filter has a method called doSomethingBeforeWrite, the attribute before-write will need to be set with name doSomethingBeforeWrite. In some cases, the memory capacity of an individual application is not capable of holding all the information in the local application memory. When this happens, the desired solution will be to hold only a portion of the information in the application's memory and the rest in a separate process(s). This mode is also known as two-level cache. In this mode, the cache is divided into two components, local cache and master cache. The local cache always resides in the physical address space of the application and the master cache runs in a different process. The master cache is used to share data among the different embedded local caches running within other application instances. In this mode, when a read/get operation is called, a matching object is first looked up in the local embedded cache. If the object is not found in the local cache, it will be searched for in the master cache. If it is not found in the master cache, it will reload the data from the data source. Updates on the central cache will be propagated into all local embedded cache instances in either pull or push mode, using unicast or multicast protocol. Sets additional properties for the local cache. ". ]]> The Space to build the local cache on top. When the connection between a local cache and remote master space is disrupted, the local cache starts trying to reconnect with the remote space. If the disconnection duration exceeds the max-disconnection-duration, the local cache enters a disconnected state, wherein each operation throws an exception stating the cache is disconnected. When the connection to the remote master space is restored, the local cache state will resume to a connected state. Determines the threshold batch size for synchronizing the local cache. Determines the threshold batch time for synchronizing the local cache. The maximum time (in milliseconds) an object will live in the local cache before being evicted. The size of the local cache. Controls how updates are reflected in the local cache. Each update triggers an invalidation event at every cache instance. The invalidate event marks the object in the local cache instances as invalid. Therefore, an attempt to read this object triggers a reload process in the master space. This configuration is useful in cases where objects are updated frequently, but the updated value is required by the application less frequently. The master pushes the updates to the local cache, which holds a reference to the same updated object. The local cache will not register for master space updates - If an object is changed in the master space, it will remain stale in the local cache until its lease expires. The space local view proxy maintains a subset of the master space's data, allowing the client to read distributed data without any remote operations. Data is streamed into the client view in an implicit manner - as opposed to local cache data, that is loaded into the client on- demand, and later updated or evicted. ". ]]> View (SQL) query controlling the data streamed to the local view. The Space to build the local view on top. When the connection between a local view and remote master space is disrupted, the local view starts trying to reconnect with the remote space. If the disconnection duration exceeds the max-disconnection-duration, the local view enters a disconnected state, wherein each operation throws an exception stating the view is disconnected. When the connection to the remote master space is restored, the local view state will resume to a connected state. Determines the threshold batch size for synchronizing the local view. Determines the threshold batch time for synchronizing the local view. GigaSpace interface providing a simplified programming model on top of IJSpace and JavaSpace interfaces. Allows to use declarative transactions and simplified API. Defines a single document type for the space The IJSpace to wrap using GigaSpace Cluster flag controlling if this GigaSpace will work with a clustered view of the space or directly with a cluster member. By default if this flag is not set it will be set automatically by this factory. It will be set to true if the space is an embedded one AND the space is not a local cache proxy. It will be set to false otherwise (i.e. the space is not an embedded space OR the space is a local cache proxy). Sets the default read timeout for #read(Object) and #readIfExists(Object) operations. Default to NO_WAIT. Sets the default take timeout for #take(Object) and #takeIfExists(Object)} operations. Default to NO_WAIT. Sets the default write lease for write(Object) operation. Default to FOREVER. Sets the transaction manager this GigaSpace interface will work with when using declarative transactions. This interface extends java.util.Map interface and provides Map interface to GigaSpaces. The IMap interface can be used in remote , embedded and Master-Local Topology. The Map interface provides three collection views, which allow a map's contents to be viewed as a set of keys, collection of values, or set of key-value mappings. You can associate attributes to a key and values (e.g. security tags, special user profiles, etc.), and set time for entries to exist in the cache until eviction. When set, the map will a local cache. Controls if this local cache will be versioned or not. Note, when settings this to true, make sure that the actual space is versioned as well. The eviction strategy for the local cache. If set to UPDATE_MODE_PULL each update triggers an invalidation event at every cache instance. The invalidate event marks the object in the local cache instances as invalid. Therefore, an attempt to read this object triggers a reload process in the master space. This configuration is useful in cases where objects are updated frequently, but the updated value is required by the application less frequently. If set to UPDATE_MODE_PUSH the master pushes the updates to the local cache, which holds a reference to the same updated object. Each update triggers an invalidation event at every cache instance. The invalidate event marks the object in the local cache instances as invalid. Therefore, an attempt to read this object triggers a reload process in the master space. This configuration is useful in cases where objects are updated frequently, but the updated value is required by the application less frequently. The master pushes the updates to the local cache, which holds a reference to the same updated object. Local cache updates can be sent via unicast or multicast. When using multicast, make sure MulticastNotifyWorker as part of the space schema configuration is enabled. Default to false. When performing a put operation, you may perform the put operation both into the local cache and the master space. This will speed up subsequent get operations. Default to true. Sets the size limit of the local cache. Default to 100000. The IJSpace to build the IMap on top Cluster flag controlling if this GigaSpace will work with a clustered view of the space or directly with a cluster member. By default if this flag is not set it will be set automatically by this factory. It will be set to true if the space is an embedded one AND the space is not a local cache proxy. It will be set to false otherwise (i.e. the space is not an embedded space OR the space is a local cache proxy). Sets the compression level. Defaults to0. GigaMap interface providing a simplified programming model on top of IMap interface. It also extends java.util.Map. It Allows to use declarative transactions and simplified API. The IMap to wrap using GigaMap Sets the default time to live (in milliseconds) for new entries. Defaults to FOREVER. Sets (in milliseconds) the default wait timeout when perfoming #get(Object) or #remove(Object). Defaults to NO WAIT (0). Sets (in milliseconds) the default time to live for locks. Defaults to 60 seconds. Sets (in milliseconds) the default time to wait for a given lock when locking. Defaults to 10 seconds. Sets the transaction manager this GigaMap interface will work with when using declarative transactions. Spring transaction manager using GigaSpaces LocalJiniTransactionManager. Local transaction manager is high performance single space transaction manager and should be used in most if not all space related operations. The IJSpace to use when starting the local transaction. Sets if this local transaction manager will work on top of a clustered Space, or will work directly with a cluster member. Spring transaction manager using GigaSpaces MahaloJiniTransactionManager. Starts an embedded mahalo (a distributed transaction manager) that can be used to perform distributed operations (on more than one resource). Note, this transaction manager is not registered for lookup. Finds a Jini transaction manager that can span transactions over several Spaces. The transaction manager name the Jini transaction manager is registered under. Optional and by default searches for all transaction managers (and finds one of them). The lookup timeout (in millis) to wait in order to find the Jini transaction manager. Defaults to 30 seconds. A comma separated list of the groups that will be used to lookup the Jini transaction manager. Defaults to ALL groups. A comma separated list of the urls (host:port) that will be used to lookup the Jini transaction manager. If set (configured) will cause each transaction to be renewed within its timeout value. The renew duration can be controlled by attributes on this element. Controls the expected round trip time to the server. This value is set in milliseconds and defaults to 1 second. The value should be lower than the renew duration. Controls how often a transaction will be renewed (which should be lower than the transaction timeout). This value is set in milliseconds and defaults to 2 seconds. The pool size value of lease renewal managers (responsible for renewing transactions). Defaults to 1 and under heavy load should be higher. Sets the default timeout to use if TransactionDefinition#TIMEOUT_DEFAULT is used. Set in milliseconds (in order to follow the TransactionDefinition contract). Defaults to FOREVER. Sets an optional timeout when performing commit in milliseconds. If not set Transaction#commit() will be called. If set Transaction#commit(long) will be called. Sets an optional timeout when performing rollback/abort in milliseconds. If not set Transaction#abort() will be called. If set Transaction#abort(long) will be called. Allows to use the @GigaSpaceContext annotation in order to inject a GigaSpace instance using annotation. Allows to use the @GigaSpaceLateContext annotation in order to inject a GigaSpace instance using annotation when injecting it into beans that depend on a Space. A Space mode based Spring context loader allows to load Spring application context if the Space is in PRIMARY mode. The space mode context loader allows to assemble beans that only operate when a space is in a PRIMARY mode which basically applies when directly working with cluster members and not a clustered space proxy (since in such cases it will always be PRIMARY). The new Spring application context created will have the current context as its parent, allowing to use any beans defined within the current context within the loaded context. The location of the Spring xml context application to be loaded. Can use Spring Resource abstraction allowing to use the classpath: prefix. Allows to set the GigaSpace instance that will control (based on its Space mode - PRIMARY or BACKUP) if the context will be loaded or not. Useful when more than one space is defined within a Spring context. Controls if the Spring context will be loaded when the space cluster member moves to PRIMARY mode. Defaults to true. A Space mode based Spring context loader allows to load Spring application context if the Space is in PRIMARY mode. The space mode context loader allows to assemble beans that only operate when a space is in a PRIMARY mode which basically applies when directly working with cluster members and not a clustered space proxy (since in such cases it will always be PRIMARY). The new Spring application context created will have the current context as its parent, allowing to use any beans defined within the current context within the loaded context. The context is refreshable by being exposed using OpenSpaces sync remoting. The location of the Spring xml context application to be loaded. Can use Spring Resource abstraction allowing to use the classpath: prefix. Allows to set the GigaSpace instance that will control (based on its Space mode - PRIMARY or BACKUP) if the context will be loaded or not. Useful when more than one space is defined within a Spring context. Controls if the Spring context will be loaded when the space cluster member moves to PRIMARY mode. Defaults to true. A sql query definition that can be used as a template. A local view query template. A general template definition using an Object type as the template and injected with specific properties (if needed). A sql query definition that can be used as a template. The where clause for the SQL query. The class type for the SQL query. Optional (translates to Class), and can be set using class-name as well (using String value). The class name (as String) for the SQL query. A local view query template. ". ]]> ". ]]> Controls if the replication filter will be active for backup Space instances. Defaults to true. Should the Space shutdown if the replication filter instance init method fails. Defaults to false. ". ]]> The priority of the given filter. Defaults to 0. Controls if the filter will be active when a Space instance is backup. Defaults to true. Controls if the filter is going to be enabled or not. Defauts to true. Controls if the filter is a security filter or not. Defaults to false. Controls if the Space will shutdown if the filter init method fails. Defaults to false. ". ]]> Defines a custom space type The id property definition. Id property name. Id autoGenerate type. The routing property definition. Routing property name. Basic equality index definition. The index path. Basic equality index definition. The index path. Wrapper class for the document. The type name. Indicator whether this type is replicable or not. Indicator whether this type is using optimistic locking. Indicator the fifo support for this type.