StateAdapterused when no type-specific adapter is registered with the
StateAdapterinstances by state type, as well as adapter behaviors using type lookups.
EntryAdapterused when no type-specific adapter is registered with the
EntryAdapterinstances by source type, as well as adapter behaviors using type lookups.
Journal<T>. A journal entry may be a serialized
Source<T>concrete implementation such as those defined in XOOM Lattice:
ProcessMessage, and others.
Commandtypes change, you will need to replace the defaults with your own implementations.
EntryAdaptertypes for both
Entry. These default adapters will be used automatically when the service or application has not registered a custom adapter for a given state or source type. This means that you do not need to register these default adapters with the
DefaultTextEntryAdapter. Because these are default adapters you will not need to import them into your main code, although the import statements are shown here for clarity.
TextEntry, respectively. They also deserialize from
TextEntryback to service and application object state.
ProductStateAdapteris responsible for adapting from the
Productservice/application object state to what is called the raw state and back again from raw state to the
public final int typeVersionin
State<T>. (This is an immutable variable and does not require an accessor method.)
EntryAdapterimplementations as for
World. The registration is a means to avoid the use of static variables to hold the adapter providers. It also makes it convenient for the various XOOM Symbio storage mechanisms to access the adapters when moving data into and out of the underlying databases.