Summary: A list of fixed bugs and known issues for GigaSpaces 5.0 (build 1410). Fixed Bugs | Known Issues | End of Life Notice | Schema Changes | Configuration, CLI, and Properties Changes | API Changes

Fixed Bugs

Below is a list of fixed bugs since GigaSpaces 4.1 (build 1160), and a list of known issues:

• GS-352 – Fixed problem when -Dcom.gs.home is defined using a non-existing directory.
• GS-1064 – Fixed problem when using long data type with SQLQuery.
• GS-1085 – Fixed issue when using NotifyDelegator. Un-finalized references of daemon threads deny NotifyDelegator from being garbage collected. This problem happens when using NIO communication protocol.
• GS-1085 – Fixed NullPointerException problem when performing thread initialization sequence causing race between Thread.start() and Thread init of internal structures.
• GS-1085 - Fixed problem when using backup space and notification registrations. writeObject/readObject notifyDelegatorStub arrives as null, causing Notifications from backup not to be triggered.
• GS-1085 – Fixed problem with garbage collection when performing serialization using compressed and light serialization mode.
• GS-1085 – Fixed problem with garbage collection when using persistent space.
• GS-1087 – Fixed NullPointerException when renewing lease.
• GS-1096 – Fixed problem with Multicast notifications using Fifo and Multicast Filter Lease renewal.
• GS-1106 – Fixed problem with Order by using column alias in JDBC driver.
• GS-1111 – Fixed performance issues with writeMultiple, takeMultiple, updateMultiple operations when using sync-replication.
• GS-1111 – Fixed problem causing dead-lock when using sync-replication using same UID in different cluster nodes.
• GS-1115 – Fixed cluster XML schema multicast configuration section to be shared both for sync and async replication mode.
• GS-1119 – Fixed problem with unclear message when throwing Can't allocate available space error.
• GS-1121 – Fixed problem with when using embedded clustered-proxy and calling take operation. The space should not do callback to the proxy using the reliable take mechanism.
• GS-1122 – Fixed problem with parseBoolen porblem when using JDK 1.4 at the JDBC and SQLQuery.
• GS-1123 – Fixed problem with count statement when in JDBC driver.
• GS-1125 – Fixed performance problem when performing read with timeout using NIO communication protocol.
• GS-1146 – Fixed problem with count statement in JDBC driver when using partition cluster.
• GS-1148 – Fixed problem with IReplication interface when entries in partial-replication and does not need to be replicated. The replicatable field was both in TypeTableEntry and BasicTypeTable classes resulting inconsistency. The replicatable attribute from TypeTableEntry was removed.
• GS-1190 – Fixed problem with persistent space and Class annotation causing serialization exceptions. The fix boost commit() and prepare() operations and introduction of new TypeTableEntry into the space.
• GS-1212 – Fixed problem when removing the same key twice from persistent space using indexed file.
• GS-1222 – Fixed problem with memory Recovery.
• GS-1224 – Fixed problem when using Space API and Local cache – change GarbageCollectorTask iterator to run on the values and not keys to avoid race issues.
• GS-1230 – Fixed problem when using transaction with the JDBC driver. In some cases the transaction did not committed.
• GS-1231 – Fixed problem with rownum when using JDBC driver.
• GS-1250 – Fixed problem with column name begins with "_" when using JDBC driver.
  log directory could not be created. The log directory by default is current directory.
• GS-755 – Fixed problem with space browser when exception thrown – show exception to user.
• GS-783 – Fixed concurrency issues when performing read and take operations while space removing/updating entries in the background.
• GS-837 – Fixed problem when GSresultSet.getString(COLUMN_NAME) throws NullPointerException.
• GS-850 – Fixed problem with unclear messages thrown while using NIO communication protocol.
• GS-879 – Fixed problem when calling update using WriteIfAbsent flag. In some cases the method returned wrong value.
• GS-925 – Fixed NullPointerException when performing join with JDBC driver.
• GS-937 – Fixed problem with replication thread when container undergo shutdown sequence.
• Updated C++ and .Net examples. Linux examples works now. Updated C++ and .Net packages places for Caching edition. .Net and C++ folder exists in EE in zipped file.
• GS-1292 – Fixed problem with system properties. Do not set system properties into Custom properties during spaceurl parsing. The only way to have system prop in custom properties is to set explicitly -Dxxx key in the properties file/object.
• GS-1287 – Fixed problem when there is attempt to run embedded container and content with such name was already created before (even with different schemaName, clusterName, etc.) throw FinderException, because container name is unique within JVM.
• GS-850 – Fixed problem with memory utilization and direct reference with NIO where referenced objects where not replicated or written to space. Reset NIO streams on every operation. This drops the performance in 7% but keeps consistent direct reference update and avoid out of memory problems (com.gs.nio.reset=1 is now default).
• GS-1288 – Fixed problem when using FIFO mode. The FIFO type indicator in the type-directory is always determined by the first operation to introduce it, regardless of the operation itself. Thus, a read/take operation can introduce a type with FIFO true, while a subsequent write is performed with FIFO false. In such a case, an InvalidFifoClassException is thrown. Resolution: InvalidFifoClassException and InvalidFifoTemplateException should retain their original logic. InvalidFifoClassException should not be thrown when a read/take with FIFO=false is performed prior to a write/snapshot/update with FIFO=true. i.e. the FIFO class-type indicator will be determined only when introducing a class by a non-template operation.
• GS-1299 – Fixed problem with QueryProcessorWorker. Did not close the socket when calling the clean operation.
• GS-1085 – Fixed problem with garbage collection closing space.
• GS-1320 – Fixed problem when using local cache with the JavaSpace API. LeaseRenewalManager causes excessive renewals, which takes 100% CPU and cause OutOfMemory. Removed static instance from declaration.
• GS-1321 – Fixed problem when using transaction with the persistent and swap space schemas.
• GS-1322 – JMS examples added.
• GS-748 – Fixed problem when using the update operation using UPDATE_OR_WRITE modifier without using UID.
• GS-1288 – Fixed problem when UnknowTypeException thrown to the source node with replication policy.
• GS-1256 – Fixed problem with cluster schema causing spaced to move into StandbyMode. Changed fail-back from false to true for the following schemas: async-repl-sync2backup-cluster-schema.xsl, async_replicated-cluster-schema.xsl, partitioned-cluster-schema.xsl, sync_replicated-cluster-schema.xsl.
• GS-1330 – Fixed problem notify lease renewal.
• GS-1320 – Fixed problem with JavaSpaces API local cache. KeepAlive mechanism fails to renew notification-template when the same proxy is found after an attempt to reconnect. Resolution:
  • Added debug messages to LeaseRenewalEvents.
  • Close NotifyDelegator before renewal of notification-template to release resources.
  • Removed constraint of creating a new NotifyDelegator when using the same proxy.
• GS-1333 – Fixed problem with LeaseManager – allowed renewals/cancellations of expired leases. LeaseManager.renew/cancel should throw UnknownLeaseException when trying to renew/cancel an already expired lease. Currently, only if the LeaseManager was awakened to traverse the leases, subsequent renewals/cancellations throws this exception. Otherwise, until awakened, renewal attempts will succeed.
• Service Grid Enhancements: Multi-network card support: providing common configuration for setting NIC , Partitioned Backup Cluster Support, Added advanced option to the deployment wizard.
• GS-1384 – J2EE Examples for IBM, BEA and JBoss application servers have been updated. A Servlet test was added to test all the space operations methods at one go.
• GS-1360 – Date and Time Format support. The space schema file includes parameters that defines the space Date, Time and DateTime formats. These are used when performing queries using the JDBC and JavaSpaces SQLQuery interface.
• GS-1337 – Do not allow to perform Query for non-comparable fields – when performing comparison with Extended match codes, on a non-comparable field ClassCastException is thrown. The fix throws UnusableEntryException with detailed description of the non-comparable field.
• GS-1357 – IJSpace.update and IMap.put performance improvement in remote mode.
• GS-1343 – Taken entries are cleaned, after commit, in a "post commit" thread activity, so new write with same UID will fail.
• GS-1339 - The IRemoteJSpaceAdmin.spaceCopy() has been modified to provide more information about the copy operation. The SpaceCopyStatus provides detailed information about the result of the copy operation.
• GS-1339 – Memory recovery fix. If during recovery the source space failed, target space is cleaned and search for available recovery-source member is continued.
• GS-1364 – Improve replication serialization to multiple targets. This enhancement is relevant only when replication-output filter is not defined and there are more than two live target nodes. Performance with 3 nodes will be improved in 3%, performance with 6 nodes will be improved in 9%.
• GS-1394 – When performing lease operations (cancel, renew) on a Lease obtained by write to a partition (clustered proxy), the Lease returned reflects a single non-clustered proxy. Thus, renewing a lease of an entry that was written to the clustered space results in UnkownLeaseException.
• GS-1336 – Allow take and write operations using the same Entry UID to be performed under transaction. In previous versions EntryAlreadyInSpaceException was thrown.
• GS-1203 – New addition – if -Dcom.gs.jini.logging.overwrite=true Java logging properties file is not overridden.
• GS-1375 – Ping command supports Jini unicast and space url options (e.g. Ping -url <full SpaceURL>).
• GS-1342 – Improvement with lookup finder – the ServiceDiscoveryListener and the LookupCache used to discover existing spaces.
• GS-1340 – Fix issue with the benchmark when using local transaction – the last performed iteration coult not commit.
• GS-1349 – Add <explicit-gc> parameter to space configuration and browser. This parameter enforce GS call when eviction thread activity started. This is usfull in heavy load situations.
• GS-1361 – When running in master-local mode client leaves open threads and not collected by GC, due to references from worker threads.
• GS-1389 – Fix issue with benchmark when using the -f and -cache options.
• GS-1395 – JDBC Procedure Call support has been introduced. This allow calling JDBC components at the server side.
• GS-1396 – Expression match code (regular expression templates - e.g RegExQuery templates) were not replicated.
• GS-1396 – Fix an issue when using the Map API get operation using remote space – Read Statistics were not updated.
• GS-1359 – ifExist behavior change – the IfExists API's (takeIfExists, readIfExists, update) were checking for exiting matching entries and tracked these, up to the specified timeout limit - until the operation performed or time out expired or when there were no valid candidates out of the initial candidates group. Newly generated matching entries where not considered as candidates, only the initial group observed in the point of time when the API called. The JavaSpaces specification is not clear regarding the exact behavior in such case. As part of the JavaSpaces-2005 spec there was a debate and the outcome was left to the decision of the implementer. With Previous versions new entries where considered as candidates but the space tracked only the initial group. Starting with build 1401 the candidate model has been modified to allow new incoming entries to be considered as part of matching entries.
• GS-1399 – Remote space operations performance have been improved. Do not use the com.gs.nio.reset parameter any more. This might cause slow performance.
• GS-787 – When running in versioned mode (optimistic locking) using the JavaSpaces API the Entry object holds implicitly the UID and version ID. Any attempts to write an entry that has just been written to the space will result EntryAlreadyExistsException.

Known Issues

• J2EE certification for Weblogic 8, JBoss 4 and IBM Webshpere 5 only.
• Replication Filter take operation does not provide Entry Meta data (ClassName Field Names, Field Types etc.) except the UID.
• When using the update operation with the UPDATE_OR_WRITE modifier with timeout >0 with non-clustered space and the relevant entry is locked under another transaction that is rolled back EntryNotInSpaceException is thrown instead of having successful operation.
• Problems when installing product at a folder that include spaces.
• CacheStore does not support notify templates.
• Recovery from persistency using Indexed file works with auto commit only.
• Open issue with registration of notifications on objects written with UID.
• When running large clusters with replicated spaces and having the recovery option turned on, it takes long time for all cluster members to move into active mode. The recovery time is a function of the number of members /* multicast timeout.
• Performance issue when using the com.j_spaces.map.eviction.LFUEvictionStrategy with multi threaded application using the same IMap instance.
• Generic SA (persistency into indexed file) does not support FIFO operations (take,notify).
• sync-rec-ack replication mode do not support replication filter – UnknownTypeException is thrown in such a case.
• Writing an Entry class with SerialVersionID different than space process Entry SerialVersionID results connection reset by peer exception.
• Multicast port opened when using unicast with replication Matrix.
• ClassCircularityError thrown in the following scenarios: Jini service running as of J2EE application server using JDK 1.4 or gsServer using JDK 1.4 with semi-dynamic clustering. Workaround – use gsInstance instead of gsServer using -Xbootclasspath/p:%XML_JARS% and run the Jini Transaction Manager as a separate process if required.
• When using any JDK 1.4 or MacOS JDK 1.5 with the partitioned-sync2backup cluster schema you should have Xbootclasspath/p:<GigaSpaces Root>\lib\xml\xalan.jar as part of the JVM running the space.
• When using the Map API get operation using embedded space – read statistics are not updated.
• Distributed transactions are not supported with persistent space using Generic SA.
• Fifo is not supported for Notifications for Take operation.
• Persistent and swap schemas do not evict data from space based on available memory but only base on amount of entries stored within the space (default 100000 entries). To turn on eviction based on available memory use the following property: com.gs.memory_usage_enabled=true.

End of Life Notice

• Embedded tomcat – replaced with Rio Webster HTTPD.
• Web services communication protocol.
• One Click Cluster – we encourage users to use the schema based cluster startup via the space URL.
• Distributed collections services – the com.j_spaces.atoms package has been removed from the API – Queue can be implemented via JMS API, Map can be implemented via the Map API.
• MDN – The com.j_spaces.dc.mdn package has been removed – the Service Grid allows dynamic spaces deployment in cluster configuration.
• Jini JMX connector – you can access GigaSpaces MBean without the Jini connector.
• End of Life for the following classes:
  • com.j_spaces.core.cluster.SyncPacket
  • com.j_spaces.core.EntryPacket
  • com.j_spaces.jmx.jini.IJiniConnector
  • com.j_spaces.jmx.jini.IJiniConnectorServer
  • com.j_spaces.jmx.jini.JiniConnectorClient
  • com.j_spaces.jmx.jini.JiniConnectorException
  • com.j_spaces.jmx.jini.JiniConnectorClient
  • com.j_spaces.atoms.IRemoteCollectionFactory
  • com.j_spaces.atoms.IRemoteJSList
  • com.j_spaces.atoms.IRemoteJSMap
  • com.j_spaces.atoms.IRemoteJSQueue
  • com.j_spaces.atoms.IRemoteJSSet
  • com.j_spaces.atoms.IRemoteJSMap.KeyValPair
  • com.j_spaces.atoms.JSList
  • com.j_spaces.atoms.JSMap
  • com.j_spaces.atoms.JSQueue
  • com.j_spaces.atoms.JSSet
  • com.j_spaces.dc.mdn.IMdn
  • com.j_spaces.dc.mdn.IMdnConnectPolicy
  • com.j_spaces.worker.marshaling.IExternalizableEntry
• The following methods have been removed from com.j_spaces.core.IJSpace:
  • Entry getEntryFromEntryPacket(EntryPacket entryPacket)
  • Entry getEntryFromEntryPacket(EntryPacket entryPacket, boolean getExternalEntry)

Schema Changes

• min_ext_index_activation_size default value – <min_ext_index_activation_size>10</min_ext_index_activation_size> changed to <min_ext_index_activation_size>1</min_ext_index_activation_size>.
  The following space schemas have been changed:
  • swap-space-schema.xml
  • persistent-space-schema.xml
  • default-space-schema.xml
  • cache-space-schema.xml
    This will turn on the extended indexing for the first Entry written in the space.
• Primary_backup broadcast-condition default value – <broadcast-condition>broadcast-if-null-values</broadcast-condition> changed to
  <broadcast-condition>broadcast-disabled</broadcast-condition> in the Primary_backup-cluster-schema.xml schema.
  The Primary_backup schema does not support broadcast operations (read, take and notify).
• async-repl-sync2backup-cluster replicate-notify-templates and trigger-notify-templates default value – <replicate-notify-templates>false</replicate-notify-templates>, <trigger-notify-templates>true</trigger-notify-templates> changed to
  <replicate-notify-templates>true</replicate-notify-templates>, <trigger-notify-templates>false</trigger-notify-templates>.
  The async-repl-sync2backup should have notify templates to be replicated.
  Notification as a result of replication event should not be triggered.
• New Cluster schema hold-txn-lock:

  <sync-replication>
  <todo-queue-timeout>1500</todo-queue-timeout>
  <hold-txn-lock>true</hold-txn-lock>
  </sync-replication>

  See CORE-3 below for details about the <hold-txn-lock> option.

• DB-22 – Fixed problem with persistent and swap schemas - <Sync_On_Commit> property was not loaded from space schema file. False value was used by default.
• DB-6 – Fixed problem with incorrect handling when using SQLQuery and JDBC queries using OR condition and brackets.
• DB-14 – Fixed problem with Query Processor – space restart did no restarted query processor.
• CORE-3 – New option has been added to cluster replication group configuration <hold-txn-lock>. This option supports explicit blocking of user thread when transaction commit occurs and data replicated to other spaces occurs using sync replication.
• CORE-138 – Fixed problem when issuing a take and write for same UID under a transaction casuing EntryAlreadyInSpace to be thrown.
• DB-24 – Fixed problem when using FIFO with sync replication causing UnknownTypeException.
• GS-1443 – Fixed problem when using persistent space using sync-replication in failover and failback events allowing the spaces to recover correctly.
• CORE-198 – Fixed problem using Sync Replication with primary backup schema with transactional operations causing performance drop.
• CORE-222 – Fixed problem with failover event when using local space load-balancing. Partition didn't fail to correct space.
• GS-1394 – Fixed problem when using embedded proxy with partitioned cluster.
  ClassCastException – cannot cast com.j_spaces.core.lrmi.LRMIRemoteSpaceImpl com.j_spaces.core.JSpaceImpl was thrown.

Configuration, CLI, and Properties Changes

• Prior to this release when using the SpaceFinder it was required to pass different system properties such as security policy, com.gs.home etc. With this release there is no need to pass any system property as part of the command line.
• The dependency on com.gs.home has been removed.
• Group configuration was configured using the group argument in the space url as well as through a system property. As of the 5.0 release group could be part of the url only i.e. there is no need to set the group using additional system property. The default group is set with value of <gigaspaces><version> instead of the default "public" convention.
• The LUS_HOST environment variable defined as part of the setenv renamed to INET_ADDR environment variable to enable setup in multiple nic environments.
• Classpath definition has been simplified through the use of manifest class-path definition. This means that users need only to place the location of the JSpaces.jar as part of their application classpath and the rest of the required jars will be loaded based on their relative location to the JSpaces.jar location. When copying the JSpaces.jar to your development directory or to your deployment directory please make sure you copy the required jars located under the relevant directory under <GigaSpaces root>\lib.
  Here is the list of required jars for client application:
  • <GigaSpaces root>\lib\JSpaces.jar
  • <GigaSpaces root>\lib\jini\jsk-platform.jar
  • <GigaSpaces root>\lib\jini\jsk-lib.jar
  • <GigaSpaces root>\lib\jini\start.jar
  • <GigaSpaces root>\lib\rio\webster.jar
  • <GigaSpaces root>\lib\common\backport-util-concurrent.jar
  • <GigaSpaces root>\lib\rio\boot.jar
  • <GigaSpaces root>\lib\log4j\log4j.jar

Below is a detailed list of config, CLI, and properties changes:

API Changes

The product API Javadoc is located at: http://www.gigaspaces.com/docs/JavaDoc.

New Interfaces:

• com.j_spaces.core.IGSEntry
• com.j_spaces.core.filters.entry.IFilterEntry extends IGSEntry
• com.j_spaces.core.filters.entry.ISpaceFilterEntry extends IFilterEntry
• com.j_spaces.core.cluster.IReplicationFilterEntry extends IFilterEntry
• com.j_spaces.kernel.time.ITimeProvider
• com.j_spaces.sadapter.GenericPA.IBasicPersistence
• com.j_spaces.sadapter.GenericPA.IMultipleOperations
• com.j_spaces.sadapter.GenericPA.IQueryblePersistentAdapter
• com.j_spaces.sadapter.GenericPA.ITransactionalPersistentAdapter
• com.j_spaces.javax.cache.Cache
• com.j_spaces.map.IMap
• com.j_spaces.javax.cache.CacheEntry
• com.j_spaces.javax.cache.CacheLifeCycleManager
• com.j_spaces.javax.cache.CacheListener
• com.j_spaces.javax.cache.CacheLoader
• com.j_spaces.javax.cache.CacheStore
• com.gigaspaces.management.SystemComponentMBean
• com.gigaspaces.grid.worker.GigaSpaceWorker
• com.gigaspaces.grid.worker.SpaceStation
• com.gigaspaces.grid.master.Job
• com.gigaspaces.grid.master.JobSubmission
• com.gigaspaces.grid.gsc.GSC

New Modifiers:

• com.j_spaces.core.client.ReadTakeModifiers
• com.j_spaces.core.client.TransactionInfo.Types
• com.j_spaces.core.client.UpdateModifiers
• com.j_spaces.core.cluster.ReplicationPolicy.ReplicationPolicyDescription

New Exceptions:

• com.j_spaces.core.EntrySerializationException
• com.j_spaces.core.exception.ClusterConfigurationException
• com.j_spaces.core.exception.SpaceConfigurationException
• com.j_spaces.javax.cache.CacheException
• com.gigaspaces.grid.master.JobException

New Implementations:

• com.j_spaces.core.client.GSIterator
• com.j_spaces.core.client.TransactionInfo
• com.j_spaces.core.cluster.LoadBalanceBroadcastInfo
• com.j_spaces.core.cluster.ReplicationPolicy
• com.j_spaces.core.filters.DefaultSecurityFilter
• com.j_spaces.javax.cache.EvictionStrategy
• com.j_spaces.kernel.log.Log4jDriver
• com.j_spaces.kernel.lrmi.MarshObject
• com.j_spaces.kernel.lrmi.CompressedMarshObject
• com.j_spaces.kernel.time.RelativeTime
• com.j_spaces.kernel.time.SystemTime
• com.j_spaces.map.CacheFinder
• com.j_spaces.map.eviction.AbstractEvictionStrategy
• com.j_spaces.map.eviction.FIFOEvictionStrategy
• com.j_spaces.map.eviction.LFUEvictionStrategy
• com.j_spaces.map.eviction.LRUEvictionStrategy
• com.j_spaces.map.eviction.NoneEvictionStrategy
• com.j_spaces.map.eviction.SizeEvictionStrategy
• com.j_spaces.sadapter.GenericPA.PersistentContext
• com.j_spaces.sadapter.GenericPA.PersistentEntry
• com.j_spaces.sadapter.GenericPA.PersistentMatchTemplate
• com.gigaspaces.grid.lookup.LookupHandler
• com.gigaspaces.grid.master.ClassIdentifier
• com.gigaspaces.grid.master.Identity
• com.gigaspaces.grid.master.JobDescriptor
• com.gigaspaces.grid.master.JobResult
• com.gigaspaces.grid.master.JobSubmissionImpl
• com.gigaspaces.grid.master.Task
• com.gigaspaces.grid.master.TaskResult
• com.gigaspaces.grid.space.GigaSpacesFaultDetectionHandler
• com.gigaspaces.grid.space.SpaceHandler
• com.gigaspaces.grid.worker.AbstractSpaceWorker
• com.gigaspaces.grid.worker.GigaSpaceStationImpl
• com.gigaspaces.grid.worker.SpaceSubstrate
• com.gigaspaces.grid.worker.TaskWorker
• com.gigaspaces.management.GigaSpacesSupport
• com.gigaspaces.management.SystemCapabilities
• com.gigaspaces.management.SystemComponent
• com.gigaspaces.management.entry.JMXConnection
• com.gigaspaces.management.system.OperatingSystemType
• com.gigaspaces.management.system.cpu.CPU
• com.gigaspaces.management.system.cpu.WindowsCPUHandler
• com.gigaspaces.management.system.disk.DiskSpace
• com.gigaspaces.management.system.disk.WindowsDiskHandler

com.j_spaces.core.IJSpace Interface Changes

New Methods:

• int setUpdateModifiers(int newModifiers)
• int getUpdateModifiers()
• int setReadTakeModifiers(int newModifiers);
• int getReadTakeModifiers()

Modified methods:

• Object[] updateMultiple(Entry[] entries, Transaction transaction, long[] leases, int updateModifiers) throws UnusableEntryException, TransactionException, java.rmi.RemoteException
• Entry update(Entry updatedEntry, Transaction transaction, long lease, long timeout, int updateModifiers) throws TransactionException, UnusableEntryException, java.rmi.RemoteException, InterruptedException

com.j_spaces.core.IGSEntry

• You may convert GigaSpaces internal Entry representation (IGSEntry) to Entry or to ExternalEntry via the following methods located at com.j_spaces.core.IGSEntry:
  • Entry getEntry(IJSpace)
  • ExternalEntry getExternalEntry(IJSpace)

com.j_spaces.map.IMap Interface Changes

The IMap includes the following new methods:

• void setVersioned(boolean versioned)
• boolean isVersioned()
• String getCacheMode()

com.j_spaces.core.client.ExternalEntry Changes

• The com.j_spaces.core.client.ExternalEntry implements now both net.jini.core.entry.Entry and com.j_spaces.core.IGSEntry

com.j_spaces.core.cluster.IReplicationFilter Interface Changes

The IReplicationFilter includes the following methods:

• void init(IJSpace space,String paramUrl,ReplicationPolicy replicationPolicy)
• void process(int direction, IReplicationFilterEntry replicationFilterEntry, String remoteSpaceMemberName)
• void close()

com.j_spaces.core.filters.ISpaceFilter Interface Changes

The ISpaceFilter includes the following methods:

• init(IJSpace space, String filterId,String url,int priority)
• void process(SpaceContext spaceContext, ISpaceFilterEntry spaceFilterEntry, int operationCode)
• void process(SpaceContext spaceContext, ISpaceFilterEntry[] spaceFilterEntry, int operationCode)
• void close()

com.j_spaces.core.client.SpaceFinder Changes

The SpaceFinder includes the following new methods:

• static Object find(String urls, IJSpace space)
• static Object find(String urls, IJSpace space, LifeCycle lifeCycle)
  static Object find(String spaceURLs, IJSpace space, Properties properties, LifeCycle lifeCycle)
• static Object find(String url, Properties customProps)