September 2020 - infinispan-issues

[JBoss JIRA] (IPROTO-154) Remove methods SerializationContextInitializer.getProtoFile and getProtoFileName

by Nistor Adrian (Jira)

[ https://issues.redhat.com/browse/IPROTO-154?page=com.atlassian.jira.plugi... ] Nistor Adrian updated IPROTO-154: --------------------------------- Priority: Minor (was: Major) > Remove methods SerializationContextInitializer.getProtoFile and getProtoFileName > -------------------------------------------------------------------------------- > > Key: IPROTO-154 > URL: https://issues.redhat.com/browse/IPROTO-154 > Project: Infinispan ProtoStream > Issue Type: Enhancement > Affects Versions: 5.0.0.Final > Reporter: Nistor Adrian > Priority: Minor > > See IPROTO-152 -- This message was sent by Atlassian Jira (v7.13.8#713008)

4 years

1
0
0 / 0

[JBoss JIRA] (IPROTO-154) Remove methods SerializationContextInitializer.getProtoFile and getProtoFileName

by Nistor Adrian (Jira)

[ https://issues.redhat.com/browse/IPROTO-154?page=com.atlassian.jira.plugi... ] Nistor Adrian reassigned IPROTO-154: ------------------------------------ Assignee: Nistor Adrian > Remove methods SerializationContextInitializer.getProtoFile and getProtoFileName > -------------------------------------------------------------------------------- > > Key: IPROTO-154 > URL: https://issues.redhat.com/browse/IPROTO-154 > Project: Infinispan ProtoStream > Issue Type: Enhancement > Affects Versions: 5.0.0.Final > Reporter: Nistor Adrian > Assignee: Nistor Adrian > Priority: Minor > > See IPROTO-152 -- This message was sent by Atlassian Jira (v7.13.8#713008)

4 years

1
0
0 / 0

[JBoss JIRA] (IPROTO-154) Remove methods SerializationContextInitializer.getProtoFile and getProtoFileName

by Nistor Adrian (Jira)

[ https://issues.redhat.com/browse/IPROTO-154?page=com.atlassian.jira.plugi... ] Nistor Adrian updated IPROTO-154: --------------------------------- Status: Open (was: New) > Remove methods SerializationContextInitializer.getProtoFile and getProtoFileName > -------------------------------------------------------------------------------- > > Key: IPROTO-154 > URL: https://issues.redhat.com/browse/IPROTO-154 > Project: Infinispan ProtoStream > Issue Type: Enhancement > Affects Versions: 5.0.0.Final > Reporter: Nistor Adrian > Priority: Major > > See IPROTO-152 -- This message was sent by Atlassian Jira (v7.13.8#713008)

4 years

1
0
0 / 0

[JBoss JIRA] (IPROTO-154) Remove methods SerializationContextInitializer.getProtoFile and getProtoFileName

by Nistor Adrian (Jira)

Nistor Adrian created IPROTO-154: ------------------------------------ Summary: Remove methods SerializationContextInitializer.getProtoFile and getProtoFileName Key: IPROTO-154 URL: https://issues.redhat.com/browse/IPROTO-154 Project: Infinispan ProtoStream Issue Type: Enhancement Affects Versions: 5.0.0.Final Reporter: Nistor Adrian See IPROTO-152 -- This message was sent by Atlassian Jira (v7.13.8#713008)

4 years

1
0
0 / 0

[JBoss JIRA] (IPROTO-153) Split SerializationContextInitializer into 2 separate interfaces, one to register schemas+marshallers and one to provide access to the generated schema

by Nistor Adrian (Jira)

[ https://issues.redhat.com/browse/IPROTO-153?page=com.atlassian.jira.plugi... ] Nistor Adrian deleted IPROTO-153: --------------------------------- > Split SerializationContextInitializer into 2 separate interfaces, one to register schemas+marshallers and one to provide access to the generated schema > ------------------------------------------------------------------------------------------------------------------------------------------------------- > > Key: IPROTO-153 > URL: https://issues.redhat.com/browse/IPROTO-153 > Project: Infinispan ProtoStream > Issue Type: Enhancement > Affects Versions: 4.3.3.Final > Reporter: Nistor Adrian > Priority: Major > > We need a way to support generating marshallers without always generating a schema. > For that we can introduce a new flag in AutoProtoSchemaBuilder , marshallersOnly (default false), that will cause schema generation and registration to be skipped. > But the current form of SerializationContextInitializer interface mixes up access to the name and contents of the generated schema and the registration of generated marshallers and schemas, and if marshallersOnly=true it's unclear what getProtoFileName() and getProtoFile() should return. > To fix that we should move methods getProtoFileName() and getProtoFile() to a sub-interface called GeneratedSchema. All generated SerializationContextInitializer implementations will implement this interface, unless marshallersOnly=true, in which case they will implement SerializationContextInitializer only. > The methods will not be really moved right now, they will be temporarily kept in SerializationContextInitializer also and will only be removed for good in version 5. > > {color:#00627a} {color} -- This message was sent by Atlassian Jira (v7.13.8#713008)

4 years

1
0
0 / 0

[JBoss JIRA] (IPROTO-153) Split SerializationContextInitializer into 2 separate interfaces, one to register schemas+marshallers and one to provide access to the generated schema

by Nistor Adrian (Jira)

[ https://issues.redhat.com/browse/IPROTO-153?page=com.atlassian.jira.plugi... ] Nistor Adrian closed IPROTO-153. -------------------------------- Resolution: Duplicate Issue Duplicate of IPROTO-153 due to internet connectivity issues and double submit > Split SerializationContextInitializer into 2 separate interfaces, one to register schemas+marshallers and one to provide access to the generated schema > ------------------------------------------------------------------------------------------------------------------------------------------------------- > > Key: IPROTO-153 > URL: https://issues.redhat.com/browse/IPROTO-153 > Project: Infinispan ProtoStream > Issue Type: Enhancement > Affects Versions: 4.3.3.Final > Reporter: Nistor Adrian > Priority: Major > > We need a way to support generating marshallers without always generating a schema. > For that we can introduce a new flag in AutoProtoSchemaBuilder , marshallersOnly (default false), that will cause schema generation and registration to be skipped. > But the current form of SerializationContextInitializer interface mixes up access to the name and contents of the generated schema and the registration of generated marshallers and schemas, and if marshallersOnly=true it's unclear what getProtoFileName() and getProtoFile() should return. > To fix that we should move methods getProtoFileName() and getProtoFile() to a sub-interface called GeneratedSchema. All generated SerializationContextInitializer implementations will implement this interface, unless marshallersOnly=true, in which case they will implement SerializationContextInitializer only. > The methods will not be really moved right now, they will be temporarily kept in SerializationContextInitializer also and will only be removed for good in version 5. > > {color:#00627a} {color} -- This message was sent by Atlassian Jira (v7.13.8#713008)

4 years

1
0
0 / 0

[JBoss JIRA] (IPROTO-153) Split SerializationContextInitializer into 2 separate interfaces, one to register schemas+marshallers and one to provide access to the generated schema

by Nistor Adrian (Jira)

Nistor Adrian created IPROTO-153: ------------------------------------ Summary: Split SerializationContextInitializer into 2 separate interfaces, one to register schemas+marshallers and one to provide access to the generated schema Key: IPROTO-153 URL: https://issues.redhat.com/browse/IPROTO-153 Project: Infinispan ProtoStream Issue Type: Enhancement Affects Versions: 4.3.3.Final Reporter: Nistor Adrian We need a way to support generating marshallers without always generating a schema. For that we can introduce a new flag in AutoProtoSchemaBuilder , marshallersOnly (default false), that will cause schema generation and registration to be skipped. But the current form of SerializationContextInitializer interface mixes up access to the name and contents of the generated schema and the registration of generated marshallers and schemas, and if marshallersOnly=true it's unclear what getProtoFileName() and getProtoFile() should return. To fix that we should move methods getProtoFileName() and getProtoFile() to a sub-interface called GeneratedSchema. All generated SerializationContextInitializer implementations will implement this interface, unless marshallersOnly=true, in which case they will implement SerializationContextInitializer only. The methods will not be really moved right now, they will be temporarily kept in SerializationContextInitializer also and will only be removed for good in version 5. {color:#00627a} {color} -- This message was sent by Atlassian Jira (v7.13.8#713008)

4 years

1
0
0 / 0

[JBoss JIRA] (IPROTO-152) Split SerializationContextInitializer into 2 separate interfaces, one to register schemas+marshallers and one to provide access to the generated schema

by Nistor Adrian (Jira)

Nistor Adrian created IPROTO-152: ------------------------------------ Summary: Split SerializationContextInitializer into 2 separate interfaces, one to register schemas+marshallers and one to provide access to the generated schema Key: IPROTO-152 URL: https://issues.redhat.com/browse/IPROTO-152 Project: Infinispan ProtoStream Issue Type: Enhancement Affects Versions: 4.3.3.Final Reporter: Nistor Adrian We need a way to support generating marshallers without always generating a schema. For that we can introduce a new flag in AutoProtoSchemaBuilder , marshallersOnly (default false), that will cause schema generation and registration to be skipped. But the current form of SerializationContextInitializer interface mixes up access to the name and contents of the generated schema and the registration of generated marshallers and schemas, and if marshallersOnly=true it's unclear what getProtoFileName() and getProtoFile() should return. To fix that we should move methods getProtoFileName() and getProtoFile() to a sub-interface called GeneratedSchema. All generated SerializationContextInitializer implementations will implement this interface, unless marshallersOnly=true, in which case they will implement SerializationContextInitializer only. The methods will not be really moved right now, they will be temporarily kept in SerializationContextInitializer also and will only be removed for good in version 5. {color:#00627a} {color} -- This message was sent by Atlassian Jira (v7.13.8#713008)

4 years

1
0
0 / 0

[JBoss JIRA] (ISPN-12050) Docs: Apply consistent terminology and make improvements to Search API

by Donald Naro (Jira)

[ https://issues.redhat.com/browse/ISPN-12050?page=com.atlassian.jira.plugi... ] Donald Naro updated ISPN-12050: ------------------------------- Summary: Docs: Apply consistent terminology and make improvements to Search API (was: Clean up Search Javadocs) > Docs: Apply consistent terminology and make improvements to Search API > ---------------------------------------------------------------------- > > Key: ISPN-12050 > URL: https://issues.redhat.com/browse/ISPN-12050 > Project: Infinispan > Issue Type: Enhancement > Affects Versions: 11.0.0.Final > Reporter: Donald Naro > Assignee: Donald Naro > Priority: Major > Fix For: 12.0.0.Final > > > Need to update Javadocs for org.infinispan.query.Search to reflect changes from deprecations and removals in 11. > [https://docs.jboss.org/infinispan/11.0/apidocs/org/infinispan/query/Searc...] > Also clarify terminology and align with doc changes. -- This message was sent by Atlassian Jira (v7.13.8#713008)

4 years

1
0
0 / 0

[JBoss JIRA] (ISPN-12050) Clean up Search Javadocs

by Donald Naro (Jira)

[ https://issues.redhat.com/browse/ISPN-12050?page=com.atlassian.jira.plugi... ] Donald Naro updated ISPN-12050: ------------------------------- Description: Need to update Javadocs for org.infinispan.query.Search to reflect changes from deprecations and removals in 11. [https://docs.jboss.org/infinispan/11.0/apidocs/org/infinispan/query/Searc...] Also clarify terminology and align with doc changes. was: Need to update Javadocs for org.infinispan.query.Search to reflect changes from deprecations and removals in 11. [https://docs.jboss.org/infinispan/11.0/apidocs/org/infinispan/query/Searc...] Also clarify terminology a little to distinguish between Search and Query. "Infinispan Search" provides the capabilities. Ickle is the query language. Add clarity by separating concepts a little throughout the Javadocs instead of using query to mean search. > Clean up Search Javadocs > ------------------------ > > Key: ISPN-12050 > URL: https://issues.redhat.com/browse/ISPN-12050 > Project: Infinispan > Issue Type: Enhancement > Affects Versions: 11.0.0.Final > Reporter: Donald Naro > Assignee: Donald Naro > Priority: Major > Fix For: 12.0.0.Final > > > Need to update Javadocs for org.infinispan.query.Search to reflect changes from deprecations and removals in 11. > [https://docs.jboss.org/infinispan/11.0/apidocs/org/infinispan/query/Searc...] > Also clarify terminology and align with doc changes. -- This message was sent by Atlassian Jira (v7.13.8#713008)

4 years

1
0
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

infinispan-issues September 2020