July 2019 - infinispan-issues - Jboss List Archives

[JBoss JIRA] (ISPN-10372) Add checkstyle that prevents use of *Async with no executor from CompletionStage

by Dan Berindei (Jira)

[ https://issues.jboss.org/browse/ISPN-10372?page=com.atlassian.jira.plugin... ] Dan Berindei updated ISPN-10372: -------------------------------- Status: Resolved (was: Pull Request Sent) Fix Version/s: 10.0.0.Beta4 Resolution: Done > Add checkstyle that prevents use of *Async with no executor from CompletionStage > -------------------------------------------------------------------------------- > > Key: ISPN-10372 > URL: https://issues.jboss.org/browse/ISPN-10372 > Project: Infinispan > Issue Type: Sub-task > Reporter: Will Burns > Assignee: Will Burns > Priority: Major > Fix For: 10.0.0.Beta4, 10.0.0.Final > > > The various *Async methods of CompletionStage that don't take an explicit Executor use the core thread pool. We don't want to be using this thread pool as we have our own to use. -- This message was sent by Atlassian Jira (v7.12.1#712002)

6 years, 9 months

1
0
0 / 0

[JBoss JIRA] (ISPN-10384) Create dedicated maven-plugins repository

by Ryan Emerson (Jira)

[ https://issues.jboss.org/browse/ISPN-10384?page=com.atlassian.jira.plugin... ] Ryan Emerson updated ISPN-10384: -------------------------------- Description: In the main ISPN repo we have a plugins dir that contains our custom maven plugins used throughout our builds. Currently this dir contains the infinispan-defaults-maven-plugin for extracting code defaults to xsd and the protocol-parser-generator-maven-plugin for generating the hotrod parser. We should create a new repository under the infinispan org, e.g. github.com/infinispan/maven-plugins, to contain all of our maven plugins that do not depend on ISPN code. The infinispan-defaults-maven-plugin can't be moved as it depends on infinispan-commons. https://github.com/infinispan/maven-plugins was: In the main ISPN repo we have a plugins dir that contains our custom maven plugins used throughout our builds. Currently this dir contains the infinispan-defaults-maven-plugin for extracting code defaults to xsd and the protocol-parser-generator-maven-plugin for generating the hotrod parser. We should create a new repository under the infinispan org, e.g. github.com/infinispan/maven-plugins, to contain all of our maven plugins that do not depend on ISPN code. The infinispan-defaults-maven-plugin can't be moved as it depends on infinispan-commons. > Create dedicated maven-plugins repository > ----------------------------------------- > > Key: ISPN-10384 > URL: https://issues.jboss.org/browse/ISPN-10384 > Project: Infinispan > Issue Type: Enhancement > Components: Build > Affects Versions: 10.0.0.Beta3 > Reporter: Ryan Emerson > Assignee: Ryan Emerson > Priority: Major > Fix For: 10.0.0.Beta4 > > > In the main ISPN repo we have a plugins dir that contains our custom maven plugins used throughout our builds. Currently this dir contains the infinispan-defaults-maven-plugin for extracting code defaults to xsd and the protocol-parser-generator-maven-plugin for generating the hotrod parser. > We should create a new repository under the infinispan org, e.g. github.com/infinispan/maven-plugins, to contain all of our maven plugins that do not depend on ISPN code. > The infinispan-defaults-maven-plugin can't be moved as it depends on infinispan-commons. > https://github.com/infinispan/maven-plugins -- This message was sent by Atlassian Jira (v7.12.1#712002)

6 years, 9 months

1
0
0 / 0

[JBoss JIRA] (ISPN-10384) Create dedicated maven-plugins repository

by Ryan Emerson (Jira)

Ryan Emerson created ISPN-10384: ----------------------------------- Summary: Create dedicated maven-plugins repository Key: ISPN-10384 URL: https://issues.jboss.org/browse/ISPN-10384 Project: Infinispan Issue Type: Enhancement Components: Build Affects Versions: 10.0.0.Beta3 Reporter: Ryan Emerson Assignee: Ryan Emerson Fix For: 10.0.0.Beta4 In the main ISPN repo we have a plugins dir that contains our custom maven plugins used throughout our builds. Currently this dir contains the infinispan-defaults-maven-plugin for extracting code defaults to xsd and the protocol-parser-generator-maven-plugin for generating the hotrod parser. We should create a new repository under the infinispan org, e.g. github.com/infinispan/maven-plugins, to contain all of our maven plugins that do not depend on ISPN code. The infinispan-defaults-maven-plugin can't be moved as it depends on infinispan-commons. -- This message was sent by Atlassian Jira (v7.12.1#712002)

6 years, 9 months

1
0
0 / 0

[JBoss JIRA] (ISPN-9944) ServerNG: Security Realms

by Gustavo Fernandes (Jira)

[ https://issues.jboss.org/browse/ISPN-9944?page=com.atlassian.jira.plugin.... ] Gustavo Fernandes updated ISPN-9944: ------------------------------------ Status: Resolved (was: Pull Request Sent) Resolution: Done > ServerNG: Security Realms > ------------------------- > > Key: ISPN-9944 > URL: https://issues.jboss.org/browse/ISPN-9944 > Project: Infinispan > Issue Type: Sub-task > Components: Security, Server > Reporter: Tristan Tarrant > Assignee: Tristan Tarrant > Priority: Major > Fix For: 10.0.0.Beta4 > > > Implement the security realms using Elytron. -- This message was sent by Atlassian Jira (v7.12.1#712002)

6 years, 9 months

1
0
0 / 0

[JBoss JIRA] (ISPN-8736) REST endpoint authorization

by Tristan Tarrant (Jira)

[ https://issues.jboss.org/browse/ISPN-8736?page=com.atlassian.jira.plugin.... ] Tristan Tarrant updated ISPN-8736: ---------------------------------- Git Pull Request: https://github.com/infinispan/infinispan/pull/7109, https://github.com/infinispan/infinispan/pull/7119 (was: https://github.com/infinispan/infinispan/pull/7109) > REST endpoint authorization > --------------------------- > > Key: ISPN-8736 > URL: https://issues.jboss.org/browse/ISPN-8736 > Project: Infinispan > Issue Type: Enhancement > Components: REST, Security, Server > Reporter: Tristan Tarrant > Assignee: Tristan Tarrant > Priority: Major > > The REST endpoint does not use the authenticated user to access authz caches. We need to: > - integrate with the ServerAuthenticationProvider as used by the Hot Rod endpoint so that we can use security callbacks and retrieve a fully populated subject (including groups). This should ultimately connect with Elytron. > - add SecurityActions within the rest code > - Return 403 forbidden where needed -- This message was sent by Atlassian Jira (v7.12.1#712002)

6 years, 9 months

1
0
0 / 0

[JBoss JIRA] (ISPN-10374) Add Client Cert authenticator to the REST endpoint

by Tristan Tarrant (Jira)

[ https://issues.jboss.org/browse/ISPN-10374?page=com.atlassian.jira.plugin... ] Tristan Tarrant updated ISPN-10374: ----------------------------------- Git Pull Request: https://github.com/infinispan/infinispan/pull/7109, https://github.com/infinispan/infinispan/pull/7119 (was: https://github.com/infinispan/infinispan/pull/7109) > Add Client Cert authenticator to the REST endpoint > -------------------------------------------------- > > Key: ISPN-10374 > URL: https://issues.jboss.org/browse/ISPN-10374 > Project: Infinispan > Issue Type: Feature Request > Components: Remote Protocols, Server > Reporter: Tristan Tarrant > Assignee: Tristan Tarrant > Priority: Major > Fix For: 10.0.0.Beta4, 9.4.16.Final > > -- This message was sent by Atlassian Jira (v7.12.1#712002)

6 years, 9 months

1
0
0 / 0

[JBoss JIRA] (ISPN-8546) Add Digest authenticator to the REST endpoint

by Tristan Tarrant (Jira)

[ https://issues.jboss.org/browse/ISPN-8546?page=com.atlassian.jira.plugin.... ] Tristan Tarrant updated ISPN-8546: ---------------------------------- Git Pull Request: https://github.com/infinispan/infinispan/pull/7109, https://github.com/infinispan/infinispan/pull/7119 (was: https://github.com/infinispan/infinispan/pull/7109) > Add Digest authenticator to the REST endpoint > --------------------------------------------- > > Key: ISPN-8546 > URL: https://issues.jboss.org/browse/ISPN-8546 > Project: Infinispan > Issue Type: Feature Request > Components: Remote Protocols, Server > Reporter: Tristan Tarrant > Assignee: Tristan Tarrant > Priority: Major > Fix For: 10.0.0.Beta4, 9.4.16.Final > > -- This message was sent by Atlassian Jira (v7.12.1#712002)

6 years, 9 months

1
0
0 / 0

[JBoss JIRA] (ISPN-9623) Create Protobuf based user marshaller

by Ryan Emerson (Jira)

[ https://issues.jboss.org/browse/ISPN-9623?page=com.atlassian.jira.plugin.... ] Ryan Emerson updated ISPN-9623: ------------------------------- Status: Pull Request Sent (was: Coding In Progress) Git Pull Request: https://github.com/infinispan/infinispan/pull/7118 > Create Protobuf based user marshaller > ------------------------------------- > > Key: ISPN-9623 > URL: https://issues.jboss.org/browse/ISPN-9623 > Project: Infinispan > Issue Type: Sub-task > Components: Core > Affects Versions: 9.4.0.Final > Reporter: Ryan Emerson > Assignee: Ryan Emerson > Priority: Major > > With the internal and persistence marshaller being protobuf based, we should also provide a user marshaller implementation that utilises protostream. Users should be able to configure annotated pojos or MessageMarshaller implementations for their objects, probably via a {{SerializationContextInitializer}} implementation. -- This message was sent by Atlassian Jira (v7.12.1#712002)

6 years, 9 months

1
0
0 / 0

[JBoss JIRA] (ISPN-10354) Remove jboss-marshalling dependency from core

by Ryan Emerson (Jira)

[ https://issues.jboss.org/browse/ISPN-10354?page=com.atlassian.jira.plugin... ] Ryan Emerson updated ISPN-10354: -------------------------------- Status: Pull Request Sent (was: Open) Git Pull Request: https://github.com/infinispan/infinispan/pull/7118 > Remove jboss-marshalling dependency from core > --------------------------------------------- > > Key: ISPN-10354 > URL: https://issues.jboss.org/browse/ISPN-10354 > Project: Infinispan > Issue Type: Sub-task > Components: Core, Marshalling > Reporter: Ryan Emerson > Assignee: Ryan Emerson > Priority: Major > > Currently the core module has a hard dependency on jboss-marshalling regardless of what user marshaller is used, therefore we should make the necessary abstractions to remove this. This work compliments ISPN-9263 as it should not be necessary to have a jboss-marshalling jar on the classpath when utilising protostream marshalling. Furthermore, jboss-marshalling is not compatible with Quarkus, therefore this step is required in order for Infinispan embedded to be readily consumed via a Quarkus extension. > Removing jboss-marshalling will result in Serializable user types no longer being marshallable as default, therefore we should introduce a `infinispan-jboss-marshalling` jar that users can continue to utilise jboss-marshalling if they wish. Furthermore, it should also be possible for users to utilise {{JavaSerializationMarshaller}} as the configured user marshaller. -- This message was sent by Atlassian Jira (v7.12.1#712002)

6 years, 9 months

1
0
0 / 0

[JBoss JIRA] (ISPN-10354) Remove jboss-marshalling dependency from core

by Ryan Emerson (Jira)

[ https://issues.jboss.org/browse/ISPN-10354?page=com.atlassian.jira.plugin... ] Ryan Emerson updated ISPN-10354: -------------------------------- Status: Open (was: New) > Remove jboss-marshalling dependency from core > --------------------------------------------- > > Key: ISPN-10354 > URL: https://issues.jboss.org/browse/ISPN-10354 > Project: Infinispan > Issue Type: Sub-task > Components: Core, Marshalling > Reporter: Ryan Emerson > Assignee: Ryan Emerson > Priority: Major > > Currently the core module has a hard dependency on jboss-marshalling regardless of what user marshaller is used, therefore we should make the necessary abstractions to remove this. This work compliments ISPN-9263 as it should not be necessary to have a jboss-marshalling jar on the classpath when utilising protostream marshalling. Furthermore, jboss-marshalling is not compatible with Quarkus, therefore this step is required in order for Infinispan embedded to be readily consumed via a Quarkus extension. > Removing jboss-marshalling will result in Serializable user types no longer being marshallable as default, therefore we should introduce a `infinispan-jboss-marshalling` jar that users can continue to utilise jboss-marshalling if they wish. Furthermore, it should also be possible for users to utilise {{JavaSerializationMarshaller}} as the configured user marshaller. -- This message was sent by Atlassian Jira (v7.12.1#712002)

6 years, 9 months

1
0
0 / 0

2026

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

infinispan-issues July 2019