February 2019 - infinispan-issues

[JBoss JIRA] (ISPN-8192) Deprecate CollectionFactory

by Ryan Emerson (Jira)

[ https://issues.jboss.org/browse/ISPN-8192?page=com.atlassian.jira.plugin.... ] Ryan Emerson updated ISPN-8192: ------------------------------- Affects Version/s: 10.0.0.Beta1 (was: 9.1.0.Final) > Deprecate CollectionFactory > --------------------------- > > Key: ISPN-8192 > URL: https://issues.jboss.org/browse/ISPN-8192 > Project: Infinispan > Issue Type: Task > Affects Versions: 10.0.0.Beta1 > Reporter: Ryan Emerson > Assignee: Ryan Emerson > Priority: Major > Fix For: 10.0.0.Beta2 > > > Many of the methods in CollectionFactory are redundant and do not add any value. We should deprecate these and replace their use within our code. -- This message was sent by Atlassian Jira (v7.12.1#712002)

7 years, 1 month

1
0
0 / 0

[JBoss JIRA] (ISPN-8192) Deprecate CollectionFactory

by Ryan Emerson (Jira)

[ https://issues.jboss.org/browse/ISPN-8192?page=com.atlassian.jira.plugin.... ] Ryan Emerson updated ISPN-8192: ------------------------------- Summary: Deprecate CollectionFactory (was: Deprecate redundant methods in CollectionFactory) > Deprecate CollectionFactory > --------------------------- > > Key: ISPN-8192 > URL: https://issues.jboss.org/browse/ISPN-8192 > Project: Infinispan > Issue Type: Task > Affects Versions: 9.1.0.Final > Reporter: Ryan Emerson > Assignee: Ryan Emerson > Priority: Major > Fix For: 9.4.8.Final > > > Many of the methods in CollectionFactory are redundant and do not add any value. We should deprecate these and replace their use within our code. -- This message was sent by Atlassian Jira (v7.12.1#712002)

7 years, 1 month

1
0
0 / 0

[JBoss JIRA] (ISPN-9964) Logging incompatibility when deploying modules on older versions of WildFly

by Radoslav Husar (Jira)

[ https://issues.jboss.org/browse/ISPN-9964?page=com.atlassian.jira.plugin.... ] Radoslav Husar updated ISPN-9964: --------------------------------- Summary: Logging incompatibility when deploying modules on older versions of WildFly (was: Logging incompatibility when deploying modules on older versions of Wildfly) > Logging incompatibility when deploying modules on older versions of WildFly > --------------------------------------------------------------------------- > > Key: ISPN-9964 > URL: https://issues.jboss.org/browse/ISPN-9964 > Project: Infinispan > Issue Type: Bug > Components: WildFly modules > Affects Versions: 9.4.6.Final > Reporter: Ryan Emerson > Assignee: Ryan Emerson > Priority: Major > Fix For: 9.4.7.Final > > > Older versions of Wildfly 7.1.x still utilise jboss-logging 3.1.x, whereas the 9.4.x branch uses 3.3.x. Jboss-logging 3.3.x introduced several new method signatures, which results in a {{NoSuchMethodError}} being thrown when infinispan is embedded on a older wildfly version. -To overcome this, it is necessary to make sure that only the method signatures found in both jboss-logging 3.1.x and 3.3.x are utilised.- Explicitly including the required version of jboss-logging in the wildfly-modules ensures that no discrepancy exists. -- This message was sent by Atlassian Jira (v7.12.1#712002)

7 years, 1 month

1
0
0 / 0

[JBoss JIRA] (ISPN-9977) java.lang.NoClassDefFoundError: org/infinispan/commons/util/FastCopyHashMap$Values (wrong name: org/infinispan/commons/dataconversion/BinaryEncoder) when starting in repackaged Spring Boot jar with Java 11

by Tristan Tarrant (Jira)

[ https://issues.jboss.org/browse/ISPN-9977?page=com.atlassian.jira.plugin.... ] Tristan Tarrant commented on ISPN-9977: --------------------------------------- The Spring guys have just confirmed it is a bug at their end. We'll keep this bug open until they release a fixed version of Spring Boot 2 > java.lang.NoClassDefFoundError: org/infinispan/commons/util/FastCopyHashMap$Values (wrong name: org/infinispan/commons/dataconversion/BinaryEncoder) when starting in repackaged Spring Boot jar with Java 11 > ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- > > Key: ISPN-9977 > URL: https://issues.jboss.org/browse/ISPN-9977 > Project: Infinispan > Issue Type: Bug > Components: Spring Integration > Affects Versions: 10.0.0.Alpha3, 9.4.6.Final > Environment: * ubuntu 16.04 > * openjdk 11.0.1 > * maven 3.6.0 > * spring boot 2.1.2.RELEASE > * infinispan-spring-boot-starter 2.1.3.Final (and 2.1.4-SNAPSHOT) > Reporter: Benjamin Schröder > Assignee: Katia Aresti > Priority: Major > > The infinispan-spring-boot-starter will fail with > {code:java} > java.lang.NoClassDefFoundError: org/infinispan/commons/util/FastCopyHashMap$Values (wrong name: org/infinispan/commons/dataconversion/BinaryEncoder) > {code} > when ran in an repackaged Spring Boot jar if built and ran with Java 11. It works if built and ran with Java 8. It works with Java 11 too but only if ran with mvn spring-boot:run > It can be reproduced with the infinispan-spring-boot-samples. (see steps to reproduce). Otherwise there is a demo project linked here: https://stackoverflow.com/questions/54635814 -- This message was sent by Atlassian Jira (v7.12.1#712002)

7 years, 1 month

1
0
0 / 0

[JBoss JIRA] (ISPN-8131) SSO with OpenShift for the management console

by Ryan Emerson (Jira)

[ https://issues.jboss.org/browse/ISPN-8131?page=com.atlassian.jira.plugin.... ] Ryan Emerson closed ISPN-8131. ------------------------------ Resolution: Won't Do > SSO with OpenShift for the management console > --------------------------------------------- > > Key: ISPN-8131 > URL: https://issues.jboss.org/browse/ISPN-8131 > Project: Infinispan > Issue Type: Feature Request > Components: JMX, reporting and management > Reporter: Sebastian Łaskawiec > Assignee: Ryan Emerson > Priority: Major > -- This message was sent by Atlassian Jira (v7.12.1#712002)

7 years, 1 month

1
0
0 / 0

[JBoss JIRA] (ISPN-9983) ServerNG Rename infinispan-server-server artifact

by Ryan Emerson (Jira)

[ https://issues.jboss.org/browse/ISPN-9983?page=com.atlassian.jira.plugin.... ] Ryan Emerson reassigned ISPN-9983: ---------------------------------- Assignee: Ryan Emerson (was: Tristan Tarrant) > ServerNG Rename infinispan-server-server artifact > ------------------------------------------------- > > Key: ISPN-9983 > URL: https://issues.jboss.org/browse/ISPN-9983 > Project: Infinispan > Issue Type: Enhancement > Components: Build, Server > Affects Versions: 10.0.0.Beta1 > Reporter: Ryan Emerson > Assignee: Ryan Emerson > Priority: Major > > Currently the Server NG artifact is named {{org.infinispan:infinispan-server-server}} which is overly verbose. We could simplify the name to {{org.infinispan:infinispan-server}} or something like {{org.infinispan:infinispan-server-runtime}}. -- This message was sent by Atlassian Jira (v7.12.1#712002)

7 years, 1 month

1
0
0 / 0

[JBoss JIRA] (ISPN-9983) ServerNG Rename infinispan-server-server artifact

by Ryan Emerson (Jira)

[ https://issues.jboss.org/browse/ISPN-9983?page=com.atlassian.jira.plugin.... ] Ryan Emerson updated ISPN-9983: ------------------------------- Status: Pull Request Sent (was: Open) Git Pull Request: https://github.com/infinispan/infinispan/pull/6699 > ServerNG Rename infinispan-server-server artifact > ------------------------------------------------- > > Key: ISPN-9983 > URL: https://issues.jboss.org/browse/ISPN-9983 > Project: Infinispan > Issue Type: Enhancement > Components: Build, Server > Affects Versions: 10.0.0.Beta1 > Reporter: Ryan Emerson > Assignee: Tristan Tarrant > Priority: Major > > Currently the Server NG artifact is named {{org.infinispan:infinispan-server-server}} which is overly verbose. We could simplify the name to {{org.infinispan:infinispan-server}} or something like {{org.infinispan:infinispan-server-runtime}}. -- This message was sent by Atlassian Jira (v7.12.1#712002)

7 years, 1 month

1
0
0 / 0

[JBoss JIRA] (ISPN-9983) ServerNG Rename infinispan-server-server artifact

by Ryan Emerson (Jira)

[ https://issues.jboss.org/browse/ISPN-9983?page=com.atlassian.jira.plugin.... ] Ryan Emerson updated ISPN-9983: ------------------------------- Status: Open (was: New) > ServerNG Rename infinispan-server-server artifact > ------------------------------------------------- > > Key: ISPN-9983 > URL: https://issues.jboss.org/browse/ISPN-9983 > Project: Infinispan > Issue Type: Enhancement > Components: Build, Server > Affects Versions: 10.0.0.Beta1 > Reporter: Ryan Emerson > Assignee: Tristan Tarrant > Priority: Major > > Currently the Server NG artifact is named {{org.infinispan:infinispan-server-server}} which is overly verbose. We could simplify the name to {{org.infinispan:infinispan-server}} or something like {{org.infinispan:infinispan-server-runtime}}. -- This message was sent by Atlassian Jira (v7.12.1#712002)

7 years, 1 month

1
0
0 / 0

[JBoss JIRA] (IPROTO-89) Provide means to calculate serialised message size

by Ryan Emerson (Jira)

[ https://issues.jboss.org/browse/IPROTO-89?page=com.atlassian.jira.plugin.... ] Ryan Emerson reassigned IPROTO-89: ---------------------------------- Assignee: Adrian Nistor > Provide means to calculate serialised message size > -------------------------------------------------- > > Key: IPROTO-89 > URL: https://issues.jboss.org/browse/IPROTO-89 > Project: Infinispan ProtoStream > Issue Type: Enhancement > Affects Versions: 4.2.2.Final > Reporter: Ryan Emerson > Assignee: Adrian Nistor > Priority: Major > > In order to be able to better estimate the size of output buffers etc, it would be useful to provide a means for a user application to retrieved the anticipated size of a serialized message from an object's current state. For example, in the protobuf-java library this is exposed via {{com.google.protobuf.MessageLite#getSerializedSize}} -- This message was sent by Atlassian Jira (v7.12.1#712002)

7 years, 1 month

1
0
0 / 0

[JBoss JIRA] (IPROTO-89) Provide means to calculate serialised message size

by Ryan Emerson (Jira)

Ryan Emerson created IPROTO-89: ---------------------------------- Summary: Provide means to calculate serialised message size Key: IPROTO-89 URL: https://issues.jboss.org/browse/IPROTO-89 Project: Infinispan ProtoStream Issue Type: Enhancement Affects Versions: 4.2.2.Final Reporter: Ryan Emerson In order to be able to better estimate the size of output buffers etc, it would be useful to provide a means for a user application to retrieved the anticipated size of a serialized message from an object's current state. For example, in the protobuf-java library this is exposed via {{com.google.protobuf.MessageLite#getSerializedSize}} -- This message was sent by Atlassian Jira (v7.12.1#712002)

7 years, 1 month

1
0
0 / 0

2026

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

infinispan-issues February 2019