Uses of Interface
io.protostuff.runtime.NumericIdStrategy.Registry
Packages that use NumericIdStrategy.Registry
-
Uses of NumericIdStrategy.Registry in io.protostuff.runtime
Classes in io.protostuff.runtime that implement NumericIdStrategy.RegistryModifier and TypeClassDescriptionstatic class
This Registry is only way to register your pojos/enums/collections/maps/delegates.static class
This Registry is only way to register your pojos/enums/collections/maps/delegates.Methods in io.protostuff.runtime that return NumericIdStrategy.RegistryModifier and TypeMethodDescriptionIf you are sure that you are only using a single implementation of your interface/abstract class, then it makes sense to map it directly to its impl class to avoid writing the type.<T extends Collection<?>>
NumericIdStrategy.RegistryNumericIdStrategy.Registry.registerCollection
(CollectionSchema.MessageFactory factory, int id) Collection ids start at 1.NumericIdStrategy.Registry.registerDelegate
(Delegate<T> delegate, int id) Register aDelegate
and assign an id.NumericIdStrategy.Registry.registerEnum
(EnumIO<?> eio, int id) Enum ids start at 1.<T extends Enum<T>>
NumericIdStrategy.RegistryNumericIdStrategy.Registry.registerEnum
(Class<T> clazz, int id) Enum ids start at 1.<T extends Map<?,
?>>
NumericIdStrategy.RegistryNumericIdStrategy.Registry.registerMap
(MapSchema.MessageFactory factory, int id) Map ids start at 1.NumericIdStrategy.Registry.registerPojo
(Schema<T> schema, Pipe.Schema<T> pipeSchema, int id) Pojo ids start at 1.NumericIdStrategy.Registry.registerPojo
(Class<T> clazz, int id) Pojo ids start at 1.