June 2018 - infinispan-issues - Jboss List Archives

[JBoss JIRA] (IPROTO-59) Remove the deprecated class BaseMessage

by Adrian Nistor (JIRA)

[ https://issues.jboss.org/browse/IPROTO-59?page=com.atlassian.jira.plugin.... ] Adrian Nistor updated IPROTO-59: -------------------------------- Fix Version/s: 4.3.0.Alpha1 > Remove the deprecated class BaseMessage > --------------------------------------- > > Key: IPROTO-59 > URL: https://issues.jboss.org/browse/IPROTO-59 > Project: Infinispan ProtoStream > Issue Type: Enhancement > Reporter: Adrian Nistor > Assignee: Adrian Nistor > Fix For: 4.3.0.Alpha1 > > > This class was deprecated long time ago and can be safely removed. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

6 years, 6 months

1
0
0 / 0

[JBoss JIRA] (IPROTO-59) Remove the deprecated class BaseMessage

by Adrian Nistor (JIRA)

Adrian Nistor created IPROTO-59: ----------------------------------- Summary: Remove the deprecated class BaseMessage Key: IPROTO-59 URL: https://issues.jboss.org/browse/IPROTO-59 Project: Infinispan ProtoStream Issue Type: Enhancement Reporter: Adrian Nistor This class was deprecated long time ago and can be safely removed. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

6 years, 6 months

1
0
0 / 0

[JBoss JIRA] (IPROTO-58) Deprecate @ProtoEnum and @ProtoMessage in favor of @ProtoName

by Adrian Nistor (JIRA)

[ https://issues.jboss.org/browse/IPROTO-58?page=com.atlassian.jira.plugin.... ] Work on IPROTO-58 started by Adrian Nistor. ------------------------------------------- > Deprecate @ProtoEnum and @ProtoMessage in favor of @ProtoName > ------------------------------------------------------------- > > Key: IPROTO-58 > URL: https://issues.jboss.org/browse/IPROTO-58 > Project: Infinispan ProtoStream > Issue Type: Enhancement > Reporter: Adrian Nistor > Assignee: Adrian Nistor > Fix For: 4.3.0.Alpha1 > > > @ProtoEnum and @ProtoMessage annotations were used just for specifying a name to be used instead of the class name. They are now unified into @ProtoName to be used for both enums and messge types. The old annotations are still preserved and marked deprecated. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

6 years, 6 months

1
0
0 / 0

[JBoss JIRA] (IPROTO-58) Deprecate @ProtoEnum and @ProtoMessage in favor of @ProtoName

by Adrian Nistor (JIRA)

Adrian Nistor created IPROTO-58: ----------------------------------- Summary: Deprecate @ProtoEnum and @ProtoMessage in favor of @ProtoName Key: IPROTO-58 URL: https://issues.jboss.org/browse/IPROTO-58 Project: Infinispan ProtoStream Issue Type: Enhancement Reporter: Adrian Nistor @ProtoEnum and @ProtoMessage annotations were used just for specifying a name to be used instead of the class name. They are now unified into @ProtoName to be used for both enums and messge types. The old annotations are still preserved and marked deprecated. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

6 years, 6 months

1
0
0 / 0

[JBoss JIRA] (IPROTO-58) Deprecate @ProtoEnum and @ProtoMessage in favor of @ProtoName

by Adrian Nistor (JIRA)

[ https://issues.jboss.org/browse/IPROTO-58?page=com.atlassian.jira.plugin.... ] Adrian Nistor updated IPROTO-58: -------------------------------- Status: Open (was: New) > Deprecate @ProtoEnum and @ProtoMessage in favor of @ProtoName > ------------------------------------------------------------- > > Key: IPROTO-58 > URL: https://issues.jboss.org/browse/IPROTO-58 > Project: Infinispan ProtoStream > Issue Type: Enhancement > Reporter: Adrian Nistor > Fix For: 4.3.0.Alpha1 > > > @ProtoEnum and @ProtoMessage annotations were used just for specifying a name to be used instead of the class name. They are now unified into @ProtoName to be used for both enums and messge types. The old annotations are still preserved and marked deprecated. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

6 years, 6 months

1
0
0 / 0

[JBoss JIRA] (IPROTO-58) Deprecate @ProtoEnum and @ProtoMessage in favor of @ProtoName

by Adrian Nistor (JIRA)

[ https://issues.jboss.org/browse/IPROTO-58?page=com.atlassian.jira.plugin.... ] Adrian Nistor reassigned IPROTO-58: ----------------------------------- Assignee: Adrian Nistor > Deprecate @ProtoEnum and @ProtoMessage in favor of @ProtoName > ------------------------------------------------------------- > > Key: IPROTO-58 > URL: https://issues.jboss.org/browse/IPROTO-58 > Project: Infinispan ProtoStream > Issue Type: Enhancement > Reporter: Adrian Nistor > Assignee: Adrian Nistor > Fix For: 4.3.0.Alpha1 > > > @ProtoEnum and @ProtoMessage annotations were used just for specifying a name to be used instead of the class name. They are now unified into @ProtoName to be used for both enums and messge types. The old annotations are still preserved and marked deprecated. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

6 years, 6 months

1
0
0 / 0

[JBoss JIRA] (IPROTO-58) Deprecate @ProtoEnum and @ProtoMessage in favor of @ProtoName

by Adrian Nistor (JIRA)

[ https://issues.jboss.org/browse/IPROTO-58?page=com.atlassian.jira.plugin.... ] Adrian Nistor updated IPROTO-58: -------------------------------- Fix Version/s: 4.3.0.Alpha1 > Deprecate @ProtoEnum and @ProtoMessage in favor of @ProtoName > ------------------------------------------------------------- > > Key: IPROTO-58 > URL: https://issues.jboss.org/browse/IPROTO-58 > Project: Infinispan ProtoStream > Issue Type: Enhancement > Reporter: Adrian Nistor > Assignee: Adrian Nistor > Fix For: 4.3.0.Alpha1 > > > @ProtoEnum and @ProtoMessage annotations were used just for specifying a name to be used instead of the class name. They are now unified into @ProtoName to be used for both enums and messge types. The old annotations are still preserved and marked deprecated. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

6 years, 6 months

1
0
0 / 0

[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: -------------------------------- Affects Version/s: 3.0.5.Final > 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 > Affects Versions: 3.0.5.Final > Reporter: Adrian Nistor > Assignee: Adrian Nistor > Fix For: 4.3.0.Alpha1 > > > 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

1
0
0 / 0

[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: -------------------------------- Fix Version/s: 4.3.0.Alpha1 > 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 > Affects Versions: 3.0.5.Final > Reporter: Adrian Nistor > Assignee: Adrian Nistor > Fix For: 4.3.0.Alpha1 > > > 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

1
0
0 / 0

[JBoss JIRA] (IPROTO-57) SerializationContext.canMarshall(String 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(String typeName) implementation does not follow documented contract (was: SerializationContext.canMarshall(Stringg typeName) implementation does not follow documented contract) > SerializationContext.canMarshall(String typeName) implementation does not follow documented contract > ---------------------------------------------------------------------------------------------------- > > Key: IPROTO-57 > URL: https://issues.jboss.org/browse/IPROTO-57 > Project: Infinispan ProtoStream > Issue Type: Bug > Affects Versions: 3.0.5.Final > Reporter: Adrian Nistor > Assignee: Adrian Nistor > Fix For: 4.3.0.Alpha1 > > > 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

1
0
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

infinispan-issues June 2018