You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I would like a way to use generic marshallers without relying on deprecated methods, right now org.infinispan.protostream.impl.SerializationContextImpl looks up marshallers using a hashmap with the class as a key which doesn't find a compatible marshaller. I am currently working around this by creating a MarshallerProvider.. would you consider keeping MarshallerProvider in order to maintain this functionality?
serializationContext.registerMarshallerProvider(newMarshallerProvider() {
@OverridepublicBaseMarshaller<?> getMarshaller(StringtypeName) {
returnnull;
}
@OverridepublicBaseMarshaller<?> getMarshaller(Class<?> javaClass) {
if (AbstractActor.class.isAssignableFrom(javaClass)) {
returngetContext().getMarshaller(AbstractActor.class);
}
if (ActorObserver.class.isAssignableFrom(javaClass)) {
returngetContext().getMarshaller(ActorObserver.class);
}
if (RemoteReference.class.isAssignableFrom(javaClass)) {
returngetContext().getMarshaller(RemoteReference.class);
}
returnnull;
}
});
The text was updated successfully, but these errors were encountered:
I would like a way to use generic marshallers without relying on deprecated methods, right now org.infinispan.protostream.impl.SerializationContextImpl looks up marshallers using a hashmap with the class as a key which doesn't find a compatible marshaller. I am currently working around this by creating a MarshallerProvider.. would you consider keeping MarshallerProvider in order to maintain this functionality?
The text was updated successfully, but these errors were encountered: