[JBoss JIRA] (IPROTO-57) SerilizationContext.canMarshall(Stringg typeName) implementation does not follow documented contract
by Adrian Nistor (JIRA)
Adrian Nistor created IPROTO-57:
-----------------------------------
Summary: SerilizationContext.canMarshall(Stringg typeName) implementation does not follow documented contract
Key: IPROTO-57
URL: https://issues.jboss.org/browse/IPROTO-57
Project: Infinispan ProtoStream
Issue Type: Bug
Reporter: Adrian Nistor
Current implementation just checks if the given protobuf type name was defined in a schema file and does not also check if a marshaller was registered for it. This is a known bug that was tolerated because fixing it would break Infinispan 8.x which mistakenly took advantage of this bug. This is no longer an issue for later Infinispan versions so it is time to fix it properly.
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
6 years, 6 months
[JBoss JIRA] (IPROTO-57) SerializationContext.canMarshall(Stringg typeName) implementation does not follow documented contract
by Adrian Nistor (JIRA)
[ https://issues.jboss.org/browse/IPROTO-57?page=com.atlassian.jira.plugin.... ]
Adrian Nistor updated IPROTO-57:
--------------------------------
Summary: SerializationContext.canMarshall(Stringg typeName) implementation does not follow documented contract (was: SerilizationContext.canMarshall(Stringg typeName) implementation does not follow documented contract)
> SerializationContext.canMarshall(Stringg typeName) implementation does not follow documented contract
> -----------------------------------------------------------------------------------------------------
>
> Key: IPROTO-57
> URL: https://issues.jboss.org/browse/IPROTO-57
> Project: Infinispan ProtoStream
> Issue Type: Bug
> Reporter: Adrian Nistor
>
> Current implementation just checks if the given protobuf type name was defined in a schema file and does not also check if a marshaller was registered for it. This is a known bug that was tolerated because fixing it would break Infinispan 8.x which mistakenly took advantage of this bug. This is no longer an issue for later Infinispan versions so it is time to fix it properly.
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
6 years, 6 months