February 2019 - infinispan-issues

[JBoss JIRA] (ISPN-9687) Simple example on remote query

by Katia Aresti (Jira)

[ https://issues.jboss.org/browse/ISPN-9687?page=com.atlassian.jira.plugin.... ] Work on ISPN-9687 started by Katia Aresti. ------------------------------------------ > Simple example on remote query > ------------------------------- > > Key: ISPN-9687 > URL: https://issues.jboss.org/browse/ISPN-9687 > Project: Infinispan > Issue Type: Feature Request > Components: Demos and Tutorials > Reporter: Katia Aresti > Assignee: Katia Aresti > Priority: Major > > Add a simple examples using remote query -- This message was sent by Atlassian Jira (v7.12.1#712002)

5 years, 11 months

1
0
0 / 0

[JBoss JIRA] (ISPN-9966) Guidelines for evolving the API over time

by Katia Aresti (Jira)

[ https://issues.jboss.org/browse/ISPN-9966?page=com.atlassian.jira.plugin.... ] Katia Aresti reassigned ISPN-9966: ---------------------------------- Assignee: Katia Aresti > Guidelines for evolving the API over time > ----------------------------------------- > > Key: ISPN-9966 > URL: https://issues.jboss.org/browse/ISPN-9966 > Project: Infinispan > Issue Type: Sub-task > Components: API > Reporter: Katia Aresti > Assignee: Katia Aresti > Priority: Major > > A plan on how we plan to evolve APIs over time. > * What recommendations should developers follow when they want to add/change/remove API methods? > * At which point they should come up with new interfaces and how do users migrate from one to the other? > * When should we create new modules? When can we reuse existing API modules? -- This message was sent by Atlassian Jira (v7.12.1#712002)

5 years, 11 months

1
0
0 / 0

[JBoss JIRA] (ISPN-9966) Guidelines for evolving the API over time

by Katia Aresti (Jira)

Katia Aresti created ISPN-9966: ---------------------------------- Summary: Guidelines for evolving the API over time Key: ISPN-9966 URL: https://issues.jboss.org/browse/ISPN-9966 Project: Infinispan Issue Type: Sub-task Components: API Reporter: Katia Aresti A plan on how we plan to evolve APIs over time. * What recommendations should developers follow when they want to add/change/remove API methods? * At which point they should come up with new interfaces and how do users migrate from one to the other? * When should we create new modules? When can we reuse existing API modules? -- This message was sent by Atlassian Jira (v7.12.1#712002)

5 years, 11 months

1
0
0 / 0

[JBoss JIRA] (IPROTO-81) SerializationContext.registerMarshaller should unregister the previous Java type (if any)

by Adrian Nistor (Jira)

[ https://issues.jboss.org/browse/IPROTO-81?page=com.atlassian.jira.plugin.... ] Adrian Nistor updated IPROTO-81: -------------------------------- Git Pull Request: https://github.com/infinispan/protostream/pull/54, https://github.com/infinispan/protostream/pull/60 (was: https://github.com/infinispan/protostream/pull/54) > SerializationContext.registerMarshaller should unregister the previous Java type (if any) > ----------------------------------------------------------------------------------------- > > Key: IPROTO-81 > URL: https://issues.jboss.org/browse/IPROTO-81 > Project: Infinispan ProtoStream > Issue Type: Bug > Reporter: Adrian Nistor > Assignee: Adrian Nistor > Priority: Major > Fix For: 4.3.0.Alpha1 > > > If the previous Java type is different it is not removed and still appears to be registered and SerializationContext.canMarshall(previousJavaType) wrongly returns true. -- This message was sent by Atlassian Jira (v7.12.1#712002)

5 years, 11 months

1
0
0 / 0

[JBoss JIRA] (IPROTO-87) Prevent auto-import of java classes that are not explicitly added to ProtoSchemaBuilder.addClass

by Adrian Nistor (Jira)

[ https://issues.jboss.org/browse/IPROTO-87?page=com.atlassian.jira.plugin.... ] Adrian Nistor updated IPROTO-87: -------------------------------- Status: Resolved (was: Pull Request Sent) Resolution: Done Integrated in master. > Prevent auto-import of java classes that are not explicitly added to ProtoSchemaBuilder.addClass > ------------------------------------------------------------------------------------------------- > > Key: IPROTO-87 > URL: https://issues.jboss.org/browse/IPROTO-87 > Project: Infinispan ProtoStream > Issue Type: Enhancement > Reporter: Adrian Nistor > Assignee: Adrian Nistor > Priority: Major > Fix For: 4.3.0.Alpha1 > > > The classes of the fields of already added classes are also automatically picked up now even if they are not explicitly added with addClass. This behaviour is usually very helpful but there might be use cases where we want explicit control of classes and everything that was not added explicitly should cause an exception. A config flag should be added for this. The current behaviour should remain the default is the flag is not specified. -- This message was sent by Atlassian Jira (v7.12.1#712002)

5 years, 11 months

1
0
0 / 0

[JBoss JIRA] (IPROTO-87) Prevent auto-import of java classes that are not explicitly added to ProtoSchemaBuilder.addClass

by Adrian Nistor (Jira)

[ https://issues.jboss.org/browse/IPROTO-87?page=com.atlassian.jira.plugin.... ] Adrian Nistor updated IPROTO-87: -------------------------------- Fix Version/s: 4.3.0.Alpha1 > Prevent auto-import of java classes that are not explicitly added to ProtoSchemaBuilder.addClass > ------------------------------------------------------------------------------------------------- > > Key: IPROTO-87 > URL: https://issues.jboss.org/browse/IPROTO-87 > Project: Infinispan ProtoStream > Issue Type: Enhancement > Reporter: Adrian Nistor > Assignee: Adrian Nistor > Priority: Major > Fix For: 4.3.0.Alpha1 > > > The classes of the fields of already added classes are also automatically picked up now even if they are not explicitly added with addClass. This behaviour is usually very helpful but there might be use cases where we want explicit control of classes and everything that was not added explicitly should cause an exception. A config flag should be added for this. The current behaviour should remain the default is the flag is not specified. -- This message was sent by Atlassian Jira (v7.12.1#712002)

5 years, 11 months

1
0
0 / 0

[JBoss JIRA] (IPROTO-87) Prevent auto-import of java classes that are not explicitly added to ProtoSchemaBuilder.addClass

by Adrian Nistor (Jira)

[ https://issues.jboss.org/browse/IPROTO-87?page=com.atlassian.jira.plugin.... ] Adrian Nistor updated IPROTO-87: -------------------------------- Status: Pull Request Sent (was: Open) Git Pull Request: https://github.com/infinispan/protostream/pull/59 > Prevent auto-import of java classes that are not explicitly added to ProtoSchemaBuilder.addClass > ------------------------------------------------------------------------------------------------- > > Key: IPROTO-87 > URL: https://issues.jboss.org/browse/IPROTO-87 > Project: Infinispan ProtoStream > Issue Type: Enhancement > Reporter: Adrian Nistor > Assignee: Adrian Nistor > Priority: Major > Fix For: 4.3.0.Alpha1 > > > The classes of the fields of already added classes are also automatically picked up now even if they are not explicitly added with addClass. This behaviour is usually very helpful but there might be use cases where we want explicit control of classes and everything that was not added explicitly should cause an exception. A config flag should be added for this. The current behaviour should remain the default is the flag is not specified. -- This message was sent by Atlassian Jira (v7.12.1#712002)

5 years, 11 months

1
0
0 / 0

[JBoss JIRA] (IPROTO-87) Prevent auto-import of java classes that are not explicitly added to ProtoSchemaBuilder.addClass

by Adrian Nistor (Jira)

[ https://issues.jboss.org/browse/IPROTO-87?page=com.atlassian.jira.plugin.... ] Adrian Nistor updated IPROTO-87: -------------------------------- Status: Open (was: New) > Prevent auto-import of java classes that are not explicitly added to ProtoSchemaBuilder.addClass > ------------------------------------------------------------------------------------------------- > > Key: IPROTO-87 > URL: https://issues.jboss.org/browse/IPROTO-87 > Project: Infinispan ProtoStream > Issue Type: Enhancement > Reporter: Adrian Nistor > Priority: Major > Fix For: 4.3.0.Alpha1 > > > The classes of the fields of already added classes are also automatically picked up now even if they are not explicitly added with addClass. This behaviour is usually very helpful but there might be use cases where we want explicit control of classes and everything that was not added explicitly should cause an exception. A config flag should be added for this. The current behaviour should remain the default is the flag is not specified. -- This message was sent by Atlassian Jira (v7.12.1#712002)

5 years, 11 months

1
0
0 / 0

[JBoss JIRA] (IPROTO-87) Prevent auto-import of java classes that are not explicitly added to ProtoSchemaBuilder.addClass

by Adrian Nistor (Jira)

[ https://issues.jboss.org/browse/IPROTO-87?page=com.atlassian.jira.plugin.... ] Adrian Nistor reassigned IPROTO-87: ----------------------------------- Assignee: Adrian Nistor > Prevent auto-import of java classes that are not explicitly added to ProtoSchemaBuilder.addClass > ------------------------------------------------------------------------------------------------- > > Key: IPROTO-87 > URL: https://issues.jboss.org/browse/IPROTO-87 > Project: Infinispan ProtoStream > Issue Type: Enhancement > Reporter: Adrian Nistor > Assignee: Adrian Nistor > Priority: Major > Fix For: 4.3.0.Alpha1 > > > The classes of the fields of already added classes are also automatically picked up now even if they are not explicitly added with addClass. This behaviour is usually very helpful but there might be use cases where we want explicit control of classes and everything that was not added explicitly should cause an exception. A config flag should be added for this. The current behaviour should remain the default is the flag is not specified. -- This message was sent by Atlassian Jira (v7.12.1#712002)

5 years, 11 months

1
0
0 / 0

[JBoss JIRA] (ISPN-9965) HotRodRemoteCache*IT.testDataConversionsWithDefaultRemoteCache failures

by Tristan Tarrant (Jira)

[ https://issues.jboss.org/browse/ISPN-9965?page=com.atlassian.jira.plugin.... ] Tristan Tarrant updated ISPN-9965: ---------------------------------- Status: Pull Request Sent (was: Open) Git Pull Request: https://github.com/infinispan/infinispan/pull/6677 > HotRodRemoteCache*IT.testDataConversionsWithDefaultRemoteCache failures > ----------------------------------------------------------------------- > > Key: ISPN-9965 > URL: https://issues.jboss.org/browse/ISPN-9965 > Project: Infinispan > Issue Type: Bug > Components: Test Suite - Server > Reporter: Tristan Tarrant > Assignee: Tristan Tarrant > Priority: Major > Fix For: 10.0.0.Beta1 > > > expected:<<[]string>Hello!</strin...> but was:<<[?xml version='1.0' encoding='UTF-8'?><]string>Hello!</strin...> > Using the StAX driver with xstream has added the xml prolog to the xml responses. -- This message was sent by Atlassian Jira (v7.12.1#712002)

5 years, 11 months

1
0
0 / 0

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

infinispan-issues February 2019