June 2014 - infinispan-issues - Jboss List Archives

[JBoss JIRA] (ISPN-4331) Add searching for TransactionManager in OSGi to GenericTransactionManagerLookup

by Tristan Tarrant (JIRA)

[ https://issues.jboss.org/browse/ISPN-4331?page=com.atlassian.jira.plugin.... ] Tristan Tarrant updated ISPN-4331: ---------------------------------- Status: Resolved (was: Pull Request Sent) Fix Version/s: 7.0.0.Final Resolution: Done > Add searching for TransactionManager in OSGi to GenericTransactionManagerLookup > ------------------------------------------------------------------------------- > > Key: ISPN-4331 > URL: https://issues.jboss.org/browse/ISPN-4331 > Project: Infinispan > Issue Type: Feature Request > Components: Transactions > Affects Versions: 7.0.0.Alpha4 > Reporter: Martin Gencur > Assignee: Martin Gencur > Fix For: 7.0.0.Beta1, 7.0.0.Final > > > The current implementation is not able to find the transaction manager that is embedded in Apache Karaf. > Apache Karaf includes Apache Aries and after installing optional feature "transaction" by "feature:install transaction", the transaction manager is available through JNDI. We just need to check the right address. -- This message was sent by Atlassian JIRA (v6.2.3#6260)

9 years, 11 months

1
0
0 / 0

[JBoss JIRA] (ISPN-4011) Make it possible to use 'remote-jmx' protocol inside Karaf

by Delete Me (JIRA)

[ https://issues.jboss.org/browse/ISPN-4011?page=com.atlassian.jira.plugin.... ] Delete Me commented on ISPN-4011: --------------------------------- A fundamental property of any modular system is, that you can either use types provided by another module or embed those types, which make them an implementation detail of your module. Key is, that embedded types can indeed be treated as an implementation detail and do not show up on the module’s API. Embedding is also a way of decoupling functionality. So first should be the question, whether you want to reuse/import some already exported/provided API from some other module or want to have that as an implementation detail. The alternative approach to what I showed, is to make each API available as a separate module. OSGi is hard, in this case I recommend to go with the implementation detail approach. After all, we want to get the JMX API to work and not interface with some proprietary jboss API, right? This is just an example of how you can provide a similar bundle for infinispan. Yes, that would be it I think. > Make it possible to use 'remote-jmx' protocol inside Karaf > ---------------------------------------------------------- > > Key: ISPN-4011 > URL: https://issues.jboss.org/browse/ISPN-4011 > Project: Infinispan > Issue Type: Feature Request > Reporter: Adrian Nistor > Assignee: Martin Gencur > Labels: 630 > Fix For: 7.0.0.Final > > > This is needed so remote-query clients can register protobuf schemas via jmx. Currently this was circumvented by creating a separate stand-alone app (ProtofileRegistrar) that runs outside Karaf before the actual test. -- This message was sent by Atlassian JIRA (v6.2.3#6260)

9 years, 11 months

1
0
0 / 0

[JBoss JIRA] (ISPN-3917) Filter objects using the query DSL (without using an index)

by RH Bugzilla Integration (JIRA)

[ https://issues.jboss.org/browse/ISPN-3917?page=com.atlassian.jira.plugin.... ] RH Bugzilla Integration commented on ISPN-3917: ----------------------------------------------- Adrian Nistor <anistor(a)redhat.com> changed the Status of [bug 1102791|https://bugzilla.redhat.com/show_bug.cgi?id=1102791] from POST to MODIFIED > Filter objects using the query DSL (without using an index) > ----------------------------------------------------------- > > Key: ISPN-3917 > URL: https://issues.jboss.org/browse/ISPN-3917 > Project: Infinispan > Issue Type: Feature Request > Components: Embedded Querying > Reporter: William Burns > Assignee: Adrian Nistor > Labels: 630, roadmap > Fix For: 7.0.0.Alpha4, 7.0.0.Final > > > The cluster listeners will want to use the Query DSL for filtering and projection views. We don't want to have to tie ourselves to Lucene to do this. It was discussed to implement this using reflection. -- This message was sent by Atlassian JIRA (v6.2.3#6260)

9 years, 11 months

1
0
0 / 0

[JBoss JIRA] (ISPN-4047) Use the sort criteria provided by hql-parser (after fixing HQLPARSER-24)

by RH Bugzilla Integration (JIRA)

[ https://issues.jboss.org/browse/ISPN-4047?page=com.atlassian.jira.plugin.... ] RH Bugzilla Integration commented on ISPN-4047: ----------------------------------------------- Adrian Nistor <anistor(a)redhat.com> changed the Status of [bug 1102791|https://bugzilla.redhat.com/show_bug.cgi?id=1102791] from POST to MODIFIED > Use the sort criteria provided by hql-parser (after fixing HQLPARSER-24) > ------------------------------------------------------------------------ > > Key: ISPN-4047 > URL: https://issues.jboss.org/browse/ISPN-4047 > Project: Infinispan > Issue Type: Enhancement > Components: Embedded Querying, Remote Querying > Affects Versions: 6.0.1.Final > Reporter: Adrian Nistor > Assignee: Adrian Nistor > Labels: 630 > Fix For: 7.0.0.Beta1, 7.0.0.Final > > > Currently we have separate handling of the sort criteria in Infinispan because the JPQL parser skips it. See https://hibernate.atlassian.net/browse/HQLPARSER-24. -- This message was sent by Atlassian JIRA (v6.2.3#6260)

9 years, 11 months

1
0
0 / 0

[JBoss JIRA] (ISPN-4326) Change EntryIterator return type to be CacheEntry

by Galder Zamarreño (JIRA)

[ https://issues.jboss.org/browse/ISPN-4326?page=com.atlassian.jira.plugin.... ] Galder Zamarreño commented on ISPN-4326: ---------------------------------------- Add also a test that verifies that when the cache is non-empty and and a listener is added with a converter, the conversion is applied correctly. > Change EntryIterator return type to be CacheEntry > ------------------------------------------------- > > Key: ISPN-4326 > URL: https://issues.jboss.org/browse/ISPN-4326 > Project: Infinispan > Issue Type: Enhancement > Components: Core > Reporter: William Burns > Assignee: William Burns > Fix For: 7.0.0.Alpha5 > > > Currently the entry retriever pieces return a Map.Entry. However end users may need the metadata along with that. We need to change this to return CacheEntry instead so the Metadata is available. -- This message was sent by Atlassian JIRA (v6.2.3#6260)

9 years, 11 months

1
0
0 / 0

[JBoss JIRA] (ISPN-4202) Configure server side tests for custom cache store to use also old-API based cache store

by Jiří Holuša (JIRA)

[ https://issues.jboss.org/browse/ISPN-4202?page=com.atlassian.jira.plugin.... ] Jiří Holuša resolved ISPN-4202. ------------------------------- Resolution: Done > Configure server side tests for custom cache store to use also old-API based cache store > ---------------------------------------------------------------------------------------- > > Key: ISPN-4202 > URL: https://issues.jboss.org/browse/ISPN-4202 > Project: Infinispan > Issue Type: Task > Reporter: Martin Gencur > Assignee: Jiří Holuša > > This is for backwards compatibility. Latest ISPN server should accept a custom cache store implemented according to the old persistence API. > We should have tests for both variants - new-API based custom cache store and old-API based cache store. -- This message was sent by Atlassian JIRA (v6.2.3#6260)

9 years, 11 months

1
0
0 / 0

[JBoss JIRA] (ISPN-4339) Make config-modifier.xsl independent of version of schema

by Tomas Sykora (JIRA)

[ https://issues.jboss.org/browse/ISPN-4339?page=com.atlassian.jira.plugin.... ] Tomas Sykora updated ISPN-4339: ------------------------------- Affects Version/s: 7.0.0.Alpha4 > Make config-modifier.xsl independent of version of schema > --------------------------------------------------------- > > Key: ISPN-4339 > URL: https://issues.jboss.org/browse/ISPN-4339 > Project: Infinispan > Issue Type: Task > Affects Versions: 7.0.0.Alpha4 > Reporter: Tomas Sykora > Assignee: Tomas Sykora > Labels: testsuite > > For example rolling upgrades tests need to transform configuration xml files from different versions of Infinispan (schema 6.0, 7.0 ... etc.) Current config-modifier.xsl uses strict xmlns elements together with specification of a schema version. > Get rid of it and make it independent. So we can use just one config modifier for modification of even old XML config files coming from old server distributions. -- This message was sent by Atlassian JIRA (v6.2.3#6260)

9 years, 11 months

1
0
0 / 0

[JBoss JIRA] (ISPN-4339) Make config-modifier.xsl independent of version of schema

by Tomas Sykora (JIRA)

[ https://issues.jboss.org/browse/ISPN-4339?page=com.atlassian.jira.plugin.... ] Tomas Sykora updated ISPN-4339: ------------------------------- Component/s: Test Suite - Server > Make config-modifier.xsl independent of version of schema > --------------------------------------------------------- > > Key: ISPN-4339 > URL: https://issues.jboss.org/browse/ISPN-4339 > Project: Infinispan > Issue Type: Task > Components: Test Suite - Server > Affects Versions: 7.0.0.Alpha4 > Reporter: Tomas Sykora > Assignee: Tomas Sykora > Labels: testsuite > > For example rolling upgrades tests need to transform configuration xml files from different versions of Infinispan (schema 6.0, 7.0 ... etc.) Current config-modifier.xsl uses strict xmlns elements together with specification of a schema version. > Get rid of it and make it independent. So we can use just one config modifier for modification of even old XML config files coming from old server distributions. -- This message was sent by Atlassian JIRA (v6.2.3#6260)

9 years, 11 months

1
0
0 / 0

[JBoss JIRA] (ISPN-4339) Make config-modifier.xsl independent of version of schema

by Tomas Sykora (JIRA)

[ https://issues.jboss.org/browse/ISPN-4339?page=com.atlassian.jira.plugin.... ] Tomas Sykora updated ISPN-4339: ------------------------------- Status: Pull Request Sent (was: Open) Git Pull Request: https://github.com/infinispan/infinispan/pull/2597 Pull request sent, this is connected to server test suite. > Make config-modifier.xsl independent of version of schema > --------------------------------------------------------- > > Key: ISPN-4339 > URL: https://issues.jboss.org/browse/ISPN-4339 > Project: Infinispan > Issue Type: Task > Components: Test Suite - Server > Affects Versions: 7.0.0.Alpha4 > Reporter: Tomas Sykora > Assignee: Tomas Sykora > Labels: testsuite > > For example rolling upgrades tests need to transform configuration xml files from different versions of Infinispan (schema 6.0, 7.0 ... etc.) Current config-modifier.xsl uses strict xmlns elements together with specification of a schema version. > Get rid of it and make it independent. So we can use just one config modifier for modification of even old XML config files coming from old server distributions. -- This message was sent by Atlassian JIRA (v6.2.3#6260)

9 years, 11 months

1
0
0 / 0

[JBoss JIRA] (ISPN-4339) Make config-modifier.xsl independent of version of schema

by Tomas Sykora (JIRA)

[ https://issues.jboss.org/browse/ISPN-4339?page=com.atlassian.jira.plugin.... ] Tomas Sykora updated ISPN-4339: ------------------------------- Summary: Make config-modifier.xsl independent of version of schema (was: Make config-modifier.xsl independent on version of schema) > Make config-modifier.xsl independent of version of schema > --------------------------------------------------------- > > Key: ISPN-4339 > URL: https://issues.jboss.org/browse/ISPN-4339 > Project: Infinispan > Issue Type: Task > Reporter: Tomas Sykora > Assignee: Tomas Sykora > > For example rolling upgrades tests need to transform configuration xml files from different versions of Infinispan (schema 6.0, 7.0 ... etc.) Current config-modifier.xsl uses strict xmlns elements together with specification of a schema version. > Get rid of it and make it independent. So we can use just one config modifier for modification of even old XML config files coming from old server distributions. -- This message was sent by Atlassian JIRA (v6.2.3#6260)

9 years, 11 months

1
0
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

infinispan-issues June 2014