이 콘텐츠는 선택한 언어로 제공되지 않습니다.
6.2. Customizing Marshalling
Instead of using the default Marshaller, which may be slow with payloads that are unnecessarily large, objects may implement
java.io.Externalizable
so that a custom method of marshalling/unmarshalling classes is performed. With this approach the target class may be created in a variety of ways (direct instantiation, factory methods, reflection, etc.) and the developer has complete control over using the provided stream.
Implementing a Custom Externalizer
To configure a class for custom marshalling an implementation of org.infinispan.marshall.AdvancedExternalizer
must be provided. Typically this is performed in a static inner class, as seen in the below externalizer for a Book
class:
Once the
writeObject()
and readObject()
methods have been implemented the Externalizer may be linked up with the classes they externalize; this is accomplished with the getTypeClasses()
method seen in the above example.
In addition, a positive identifier must be defined as seen in the
getId()
method above. This value is used to identify the Externalizer at runtime. A list of values used by JBoss Data Grid, which should be avoided in custom Externalizer implementations, may be found at Section 6.3, “JBoss Data Grid Externalizer IDs”.
Registering Custom Marshallers
Custom Marshallers may be registered with JBoss Data Grid programmatically or declaratively, as seen in the following examples:
Example 6.1. Declaratively Register a Custom Marshaller
Example 6.2. Programmatically Register a Custom Marshaller
GlobalConfigurationBuilder builder = ... builder.serialization() .addAdvancedExternalizer(new Book.BookExternalizer());
GlobalConfigurationBuilder builder = ...
builder.serialization()
.addAdvancedExternalizer(new Book.BookExternalizer());