Chapter 3. New Features and Enhancements
3.1. Configurable Whitelist for Deserialization
By default the JBoss Data Grid server allows deserialization only for strings and primitives. As of this release, you can specify other Java class instances in a whitelist so that JBoss Data Grid deserializes objects that belong to those classes.
If you do not add your application classes to the whitelist, JBoss Data Grid does not deserialize objects that belong to those classes.
On the client side, you can add a whitelist to restrict deserialization to objects that belong to specific Java classes.
For more information, see the following:
- Configuring the Deserialization Whitelist in the Administration and Configuration Guide describes how to configure the JBoss Data Grid server.
- Restricting Deserialization to Specific Java Classes in the Developer Guide describes how to configure clients.
3.2. Disabling Indexing for Protobuf Schema Files
After you enable indexing for a cache, all fields of Protobuf encoded entries are indexed by default. This indexing can be inefficient when handling Protobuf message types that have many or large fields. You can now disable indexing for all Protobuf message types that are not annotated with the indexed_by_default option. For more information, see Disabling Indexing for All Protobuf Message Types in the Developer Guide.
3.3. Expose Query.getQueryString() as official API
As of this release, the org.infinispan.query.dsl.Query interface exposes the underlying Ickle query string with the Query.getQueryString() method. This applies to all queries regardless of whether the query was created by a DSL QueryBuilder or from a query string.
