API Documentation
Red Hat JBoss Data Grid 7.0
Javadocs for Red Hat JBoss Data Grid 7.0
Abstract
Javadocs for Red Hat JBoss Data Grid.
Red Hat JBoss Data Grid Javadocs
Select one of the following links to view the Red Hat JBoss Data Grid Javadocs:
API for Hot Rod Clients
The API for the Hot Rod Clients are found below:
API for Additional Components
Additional clients are included with JBoss Data Grid, and their APIs, as it pertains to JBoss Data Grid, are included below:
Configuration Schemas
Configuration schemas are XML files that contain a list of elements that may be used in configuration files to control the behavior of JBoss Data Grid. Click the link to view the Configuration Schemas.
Modified APIs
The following items have been modified in Red Hat JBoss Data Grid 7.0:
- The package containing the CDI modules has changed; all of these classes have moved from
org.infinispan.cditoorg.infinispan.cdi.embedded, and any applications utilizing CDI should have their imports updated to use the new packages. Additionally, the CDI extensions have been split into two classes:- CDI Classes that begin with
Injectedbefore the classname, such asorg.infinispan.jcache.annotation.InjectedCacheResultInterceptor. These classes are intended for use in managed environments, such as JBoss EAP. - CDI classes without
Injectedbefore the classname, such asorg.infinispan.jcache.annotation.CacheResultInterceptor- This class should be used in standalone environments.
- The Hibernate Search modules have been upgraded from 4.6 to 5.6, and as such there have been significant changes to this component. For a full list of the steps needed to migrate applications that use this component from JBoss Data Grid 6.x to 7.x refer to the Migration Guide.
Deprecated APIs
The following items have been deprecated in Red Hat JBoss Data Grid 7.0:
- Support for custom interceptors is being deprecated in JBoss Data Grid 7.0. A new method of executing custom interceptors is expected to be introduced in JBoss Data Grid 7.1. In addition, the interceptor stack is part of JBoss Data Grid's internal API, and is subject to change from release to release. Due to this it is not recommended to use custom interceptors directly from your application.
- The following methods of
RemoteCachehave been deprecated:remoteCache.getVersioned- this method has been replaced byremoteCache.getWithMetadata(Object).remoteCache.getBulk, getBulk(size)- Both of these methods have proven expensive for large data sets. TheremoteCache.retrieveEntries*methods offer a lazy, pull-style, approach which retrieves bulk data more efficiently.
Removed APIs
The following items have been removed in Red Hat JBoss Data Grid 7.0:
- The
NotifyingFutureinterface has been removed in JBoss Data Grid 7.0 and replaced withCompletableFuture. This class was replaced due toCompletableFuturebeing included as a standard class in Java 8, allowing for additional features such as chaining, implementing constructs such as conditionals, and timeouts to be utilized without introducing additional custom code. Any applications previously utilizingNotifyingFutureshould be updated to referenceCompletableFutureinstead. - Support for Spring 3 has been removed; any applications previously using Spring 3 should be rewritten to use Spring 4, instead.
- Map/Reduce has been removed in JBoss Data Grid 7.0.0. This feature has been replaced by Distributed Streams, which were shown to have better performance.
