March 2012 - infinispan-issues - Jboss List Archives

[JBoss JIRA] Created: (ISPN-1266) Add more integration tests with Arquillian

by Kevin Pollet (JIRA)

Add more integration tests with Arquillian ------------------------------------------ Key: ISPN-1266 URL: https://issues.jboss.org/browse/ISPN-1266 Project: Infinispan Issue Type: Task Components: CDI integration Reporter: Kevin Pollet Assignee: Kevin Pollet Fix For: 5.1.0.FINAL This extension should be tested with: * Open Web Beans * JBoss AS7 * GlassFish -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 1 month

5
13
0 / 0

[JBoss JIRA] Created: (ISPN-1253) Integrate the Tattletale Maven plugin into Infinispan.

by Navin Surtani (JIRA)

Integrate the Tattletale Maven plugin into Infinispan. ------------------------------------------------------ Key: ISPN-1253 URL: https://issues.jboss.org/browse/ISPN-1253 Project: Infinispan Issue Type: Task Components: Build process Reporter: Navin Surtani Assignee: Navin Surtani Priority: Minor Fix For: 5.0.0.FINAL Make use of the tattletale maven plugin for infinispan. This way there will not be issues similar to ISPN-1234 cropping up. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 1 month

6
7
0 / 0

[JBoss JIRA] (ISPN-1491) Provide methods to retrieve the CacheKey parameters

by Kevin Pollet (Created) (JIRA)

Provide methods to retrieve the CacheKey parameters --------------------------------------------------- Key: ISPN-1491 URL: https://issues.jboss.org/browse/ISPN-1491 Project: Infinispan Issue Type: Enhancement Components: CDI integration Reporter: Kevin Pollet Assignee: Kevin Pollet Fix For: 5.1.0.BETA4, 5.1.0.FINAL Currently, it's not possible to retrieve the parameter values composing the {{CacheKey}} (generated by JCache interceptors). For that, we could introduce two interfaces. * {{SimpleCacheKey<T>}} used when only one parameter is used as key. This interface could add the following method {{T getValue()}} * {{ComposedCacheKey}} used when the key is composed by more than one parameter. This interface could add the following method {{Object[] getValues()}} Here, we need to ensure that we are compliant with the specification. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 1 month

4
7
0 / 0

[JBoss JIRA] (ISPN-1627) Remove the deprecated OverrideDefault annotation

by Kevin Pollet (Created) (JIRA)

Remove the deprecated OverrideDefault annotation ------------------------------------------------ Key: ISPN-1627 URL: https://issues.jboss.org/browse/ISPN-1627 Project: Infinispan Issue Type: Task Components: CDI integration Reporter: Kevin Pollet Assignee: Kevin Pollet Fix For: 5.2.0.FINAL -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 1 month

3
2
0 / 0

[JBoss JIRA] Created: (ISPN-1262) Validate that the JCache interceptors are declared in the beans.xml

by Kevin Pollet (JIRA)

Validate that the JCache interceptors are declared in the beans.xml ------------------------------------------------------------------- Key: ISPN-1262 URL: https://issues.jboss.org/browse/ISPN-1262 Project: Infinispan Issue Type: Feature Request Components: CDI integration Reporter: Kevin Pollet Assignee: Kevin Pollet Priority: Minor We could validate that the JCache interceptors are enabled in the {{beans.xml}} at deployment. This check can be done at {{AfterBeanDiscovery}} phase with {{BeanManager#resolverInterceptors()}} for each JCache annotations. The deployment could fail only when JCache annotations are used in the application. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 1 month

2
5
0 / 0

[JBoss JIRA] Created: (ISPN-1261) Complete the work on the event bridge between Infinispan and CDI

by Kevin Pollet (JIRA)

Complete the work on the event bridge between Infinispan and CDI ---------------------------------------------------------------- Key: ISPN-1261 URL: https://issues.jboss.org/browse/ISPN-1261 Project: Infinispan Issue Type: Task Components: CDI integration Reporter: Kevin Pollet Assignee: Kevin Pollet The event bridge (for cache and cache manager) is already implemented in the code but some events are not supported and a deprecated one is used. The following work has to be done on the event bridge: * Remove deprecated event * Support all events * Verify how cache and cache manager observers are registered * Tests * Doc -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 1 month

4
12
0 / 0

[JBoss JIRA] (ISPN-1893) Query module demo

by Mathieu Lachance (JIRA)

Mathieu Lachance created ISPN-1893: -------------------------------------- Summary: Query module demo Key: ISPN-1893 URL: https://issues.jboss.org/browse/ISPN-1893 Project: Infinispan Issue Type: Task Components: Core API, Locking and Concurrency, Migration tools Reporter: Mathieu Lachance Assignee: Manik Surtani Would it be possible to make a query-module demo showing the best practice with : - replication clustering mode + local query, - distribution clustering mode + index replication + local query, - distribution clustering mode + clustered query I guess this would be easy to integrate it in the already existant gui demo. Big thanks ! -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 1 month

5
7
0 / 0

[JBoss JIRA] (ISPN-1925) Upgrade to JCache 0.5

by Kevin Pollet (JIRA)

Kevin Pollet created ISPN-1925: ---------------------------------- Summary: Upgrade to JCache 0.5 Key: ISPN-1925 URL: https://issues.jboss.org/browse/ISPN-1925 Project: Infinispan Issue Type: Component Upgrade Components: CDI integration Reporter: Kevin Pollet Assignee: Kevin Pollet Fix For: 5.2.0.ALPHA1 -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 1 month

3
8
0 / 0

[JBoss JIRA] Created: (ISPN-1407) Make sure the server_list attribute of Hot Rod can be updated dynamically

by Sanne Grinovero (JIRA)

Make sure the server_list attribute of Hot Rod can be updated dynamically ------------------------------------------------------------------------- Key: ISPN-1407 URL: https://issues.jboss.org/browse/ISPN-1407 Project: Infinispan Issue Type: Feature Request Components: Cache Server Reporter: Sanne Grinovero Assignee: Manik Surtani when starting a rolling upgrade it will be needed to upgrade the server_lists with new entries at the start of the upgrade, and possibly remove some entries when the upgrade is done -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 1 month

6
16
0 / 0

[JBoss JIRA] Created: (ISPN-1403) Optimise sending Hot Rod topology updates for distributed caches

by Galder Zamarreño (JIRA)

Optimise sending Hot Rod topology updates for distributed caches ---------------------------------------------------------------- Key: ISPN-1403 URL: https://issues.jboss.org/browse/ISPN-1403 Project: Infinispan Issue Type: Enhancement Components: Cache Server, Distributed Cache Reporter: Galder Zamarreño Assignee: Galder Zamarreño Fix For: 5.2.0.FINAL Right now, whenever a Hot Rod client sends a request with a view id which is different to the one on the server, it'd get a brand new view in the response to the request. This could be optimised nicely by only sending back a new view id when the server discovers that the client is using an inefficient view. For example, in distributed caches, the moment it gets a request for a key which lands on a node that does not own the key, it could decide to send back the view. This would reduce the number of times the view is returned, hence improving the performance of requests. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 1 month

2
1
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

infinispan-issues March 2012