January 2017 - infinispan-issues - Jboss List Archives

[JBoss JIRA] (ISPN-7343) Allow using Hibernate Search, Hibernate ORM, Hibernate OGM and Infinispan + Infinispan Query in the same app in Wildfly

by Sanne Grinovero (JIRA)

[ https://issues.jboss.org/browse/ISPN-7343?page=com.atlassian.jira.plugin.... ] Sanne Grinovero reassigned ISPN-7343: ------------------------------------- Issue Type: Feature Request (was: Bug) Component/s: Embedded Querying WildFly modules Description: We should make it easier to use all those libraries in a single app on WildFly. This is a tricky request, as Infinispan Query exposes its own version of Hibernate Search as public API: people need to use it directly to use embedded query. Not least it requires exposing: * index mapping annotations from Hibernate Search * Usage of the Hibernate Search querybuilder helpers (optional) * Direct usage of the Apache Lucene classes, in turn exposed as well as public API by Hibernate Search When wanting to use Hibernate Search directly as well (with Hibernate ORM), one needs not only to choose a version which is compatible with both, but one also needs to make sure that the WildFly modules are all using the same module id; the problem being one should not use multiple copies of the module, as the Infinispan project re-distributes its own copy of such modules. Picking a compatible version is limiting but not hard; editing all module XML definitions is not very nice though. was:We should allow to use all those libraries in a single app on WildFly. Affects Version/s: (was: 8.2.5.Final) Assignee: (was: Sanne Grinovero) > Allow using Hibernate Search, Hibernate ORM, Hibernate OGM and Infinispan + Infinispan Query in the same app in Wildfly > ----------------------------------------------------------------------------------------------------------------------- > > Key: ISPN-7343 > URL: https://issues.jboss.org/browse/ISPN-7343 > Project: Infinispan > Issue Type: Feature Request > Components: Embedded Querying, WildFly modules > Reporter: Sebastian Łaskawiec > Priority: Minor > > We should make it easier to use all those libraries in a single app on WildFly. > This is a tricky request, as Infinispan Query exposes its own version of Hibernate Search as public API: people need to use it directly to use embedded query. > Not least it requires exposing: > * index mapping annotations from Hibernate Search > * Usage of the Hibernate Search querybuilder helpers (optional) > * Direct usage of the Apache Lucene classes, in turn exposed as well as public API by Hibernate Search > When wanting to use Hibernate Search directly as well (with Hibernate ORM), one needs not only to choose a version which is compatible with both, but one also needs to make sure that the WildFly modules are all using the same module id; the problem being one should not use multiple copies of the module, as the Infinispan project re-distributes its own copy of such modules. > Picking a compatible version is limiting but not hard; editing all module XML definitions is not very nice though. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years, 2 months

1
0
0 / 0

[JBoss JIRA] (ISPN-7331) Administration console - removing task before undeploying it should show an error

by Ryan Emerson (JIRA)

[ https://issues.jboss.org/browse/ISPN-7331?page=com.atlassian.jira.plugin.... ] Ryan Emerson resolved ISPN-7331. -------------------------------- Fix Version/s: 9.0.0.Beta2 Resolution: Done Fixed by only enabling the deployment's "remove" button once a Jar has been undeployed. > Administration console - removing task before undeploying it should show an error > --------------------------------------------------------------------------------- > > Key: ISPN-7331 > URL: https://issues.jboss.org/browse/ISPN-7331 > Project: Infinispan > Issue Type: Bug > Components: Console > Affects Versions: 9.0.0.Beta1 > Reporter: Jiří Holuša > Assignee: Vladimir Blagojevic > Priority: Minor > Fix For: 9.0.0.Beta2 > > Attachments: local-task.jar > > > Steps to reproduce: > Go to cache container -> Configuration -> Deployments -> upload some task (you can use the one in attachment) -> Deploy the task -> try clicking Remove > The task is correctly not removed, since it's not undeployed yet. However, there used to be a popup windows which showed, why the task could not be removed. I think it should be put back since it's much more user-friendly. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years, 2 months

1
0
0 / 0

[JBoss JIRA] (ISPN-7344) Console Deployment uploads fail with 415 error

by Ryan Emerson (JIRA)

Ryan Emerson created ISPN-7344: ---------------------------------- Summary: Console Deployment uploads fail with 415 error Key: ISPN-7344 URL: https://issues.jboss.org/browse/ISPN-7344 Project: Infinispan Issue Type: Bug Components: Console Affects Versions: 9.0.0.Beta1 Reporter: Ryan Emerson Assignee: Ryan Emerson It's not possible to upload a deployment to the server via the console, as a 415 Unsupported media type error is always returned from the server. This is a consequence of ISPN-7310 as the use of digest authentication has changed the http request headers sent to the server. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years, 2 months

1
0
0 / 0

[JBoss JIRA] (ISPN-1947) Automate staging repository step in release script

by Sebastian Łaskawiec (JIRA)

[ https://issues.jboss.org/browse/ISPN-1947?page=com.atlassian.jira.plugin.... ] Sebastian Łaskawiec edited comment on ISPN-1947 at 1/9/17 4:18 AM: ------------------------------------------------------------------- Together with [~NadirX], we agreed that we will automate the release process. I removed all staging plugin usages in the project and we will flip back to good old deploy plugin. Automated release process will: * Create a staging profile * Upload released bits * Do some automated testing * Close it was (Author: sebastian.laskawiec): Together with [~NadirX], we agreed that we will automate the release process. I removed all staging plugin usages in the project and we will flip back to good old deploy plugin. > Automate staging repository step in release script > -------------------------------------------------- > > Key: ISPN-1947 > URL: https://issues.jboss.org/browse/ISPN-1947 > Project: Infinispan > Issue Type: Task > Components: Build process > Reporter: Sanne Grinovero > Assignee: Sebastian Łaskawiec > Priority: Critical > Fix For: 9.0.0.Beta1 > > > The Nexus staging plugin can be used to control the staging repository from command line (including authenticating with your account as set in your settings file) > https://github.com/sonatype/nexus-maven-plugins/tree/master/staging/maven... -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years, 2 months

1
0
0 / 0

[JBoss JIRA] (ISPN-1947) Automate staging repository step in release script

by Sebastian Łaskawiec (JIRA)

[ https://issues.jboss.org/browse/ISPN-1947?page=com.atlassian.jira.plugin.... ] Sebastian Łaskawiec commented on ISPN-1947: ------------------------------------------- Together with [~NadirX], we agreed that we will automate the release process. I removed all staging plugin usages in the project and we will flip back to good old deploy plugin. > Automate staging repository step in release script > -------------------------------------------------- > > Key: ISPN-1947 > URL: https://issues.jboss.org/browse/ISPN-1947 > Project: Infinispan > Issue Type: Task > Components: Build process > Reporter: Sanne Grinovero > Assignee: Sebastian Łaskawiec > Priority: Critical > Fix For: 9.0.0.Beta1 > > > The Nexus staging plugin can be used to control the staging repository from command line (including authenticating with your account as set in your settings file) > https://github.com/sonatype/nexus-maven-plugins/tree/master/staging/maven... -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years, 2 months

1
0
0 / 0

[JBoss JIRA] (ISPN-1947) Automate staging repository step in release script

by Sebastian Łaskawiec (JIRA)

[ https://issues.jboss.org/browse/ISPN-1947?page=com.atlassian.jira.plugin.... ] Sebastian Łaskawiec updated ISPN-1947: -------------------------------------- Status: Open (was: Pull Request Sent) > Automate staging repository step in release script > -------------------------------------------------- > > Key: ISPN-1947 > URL: https://issues.jboss.org/browse/ISPN-1947 > Project: Infinispan > Issue Type: Task > Components: Build process > Reporter: Sanne Grinovero > Assignee: Sebastian Łaskawiec > Priority: Critical > Fix For: 9.0.0.Beta1 > > > The Nexus staging plugin can be used to control the staging repository from command line (including authenticating with your account as set in your settings file) > https://github.com/sonatype/nexus-maven-plugins/tree/master/staging/maven... -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years, 2 months

1
0
0 / 0

[JBoss JIRA] (ISPN-7343) Allow using Hibernate Search, Hibernate ORM, Hibernate OGM and Infinispan + Infinispan Query in the same app in Wildfly

by Sebastian Łaskawiec (JIRA)

Sebastian Łaskawiec created ISPN-7343: ----------------------------------------- Summary: Allow using Hibernate Search, Hibernate ORM, Hibernate OGM and Infinispan + Infinispan Query in the same app in Wildfly Key: ISPN-7343 URL: https://issues.jboss.org/browse/ISPN-7343 Project: Infinispan Issue Type: Bug Affects Versions: 8.2.5.Final Reporter: Sebastian Łaskawiec Assignee: Sanne Grinovero Priority: Minor We should allow to use all those libraries in a single app on WildFly. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years, 2 months

1
0
0 / 0

[JBoss JIRA] (ISPN-7342) Cassandra Cache Store is missing Custom Cache Store service manifest

by Sebastian Łaskawiec (JIRA)

Sebastian Łaskawiec created ISPN-7342: ----------------------------------------- Summary: Cassandra Cache Store is missing Custom Cache Store service manifest Key: ISPN-7342 URL: https://issues.jboss.org/browse/ISPN-7342 Project: Infinispan Issue Type: Bug Components: Loaders and Stores Reporter: Sebastian Łaskawiec Assignee: Jakub Markos Currently it is not possible to use [Cassandra Cache Store|https://github.com/infinispan/infinispan-cachestore-cassandra] as a [Deployable Cache Store|http://infinispan.org/docs/stable/user_guide/user_guide.html#custom...] on the server. There are no proper {{/META-INF/services/org.infinispan.persistence.spi.AdvancedLoadWriteStore}} entry pointing to [CassandraStore|https://github.com/infinispan/infinispan-cachestore-cassan...] class. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years, 2 months

1
0
0 / 0

[JBoss JIRA] (ISPN-7341) Update the Roadmap for ISPN9

by Sebastian Łaskawiec (JIRA)

Sebastian Łaskawiec created ISPN-7341: ----------------------------------------- Summary: Update the Roadmap for ISPN9 Key: ISPN-7341 URL: https://issues.jboss.org/browse/ISPN-7341 Project: Infinispan Issue Type: Bug Affects Versions: 9.0.0.Beta1 Reporter: Sebastian Łaskawiec Assignee: Tristan Tarrant Priority: Minor Our [Roadmap page|http://infinispan.org/roadmap/] needs to get updated. The image states that 9.0 will happen in Jan *2016*. It should be *2017*. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years, 2 months

1
0
0 / 0

[JBoss JIRA] (ISPN-7339) Fix Ickle's support for named parameters

by Adrian Nistor (JIRA)

[ https://issues.jboss.org/browse/ISPN-7339?page=com.atlassian.jira.plugin.... ] Adrian Nistor updated ISPN-7339: -------------------------------- Issue Type: Bug (was: Task) > Fix Ickle's support for named parameters > ---------------------------------------- > > Key: ISPN-7339 > URL: https://issues.jboss.org/browse/ISPN-7339 > Project: Infinispan > Issue Type: Bug > Components: Embedded Querying, Remote Querying > Affects Versions: 9.0.0.Beta1 > Reporter: Adrian Nistor > Assignee: Adrian Nistor > Fix For: 9.0.0.Beta2 > > > Current implementation is incomplete. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years, 2 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 January 2017