January 2008 - jboss-jira - Jboss List Archives

[JBoss JIRA] Created: (EJBTHREE-1060) getInvokedBusinessInterface doesn't return correct interface

by Carlo de Wolf (JIRA)

getInvokedBusinessInterface doesn't return correct interface ------------------------------------------------------------ Key: EJBTHREE-1060 URL: http://jira.jboss.com/jira/browse/EJBTHREE-1060 Project: EJB 3.0 Issue Type: Bug Reporter: Carlo de Wolf Assigned To: Andrew Rubinger When there is a common super interface, getInvokedBusinessInterface doesn't return the correct interface. @Stateless @Remote({Remote1.class, Remote2.class}) interface Remote1 extends CommonRemote interface Remote2 extends CommonRemote -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

17 years, 11 months

3
3
0 / 0

[JBoss JIRA] Created: (JBREM-812) Specify an API to discover services

by David Lloyd (JIRA)

Specify an API to discover services ----------------------------------- Key: JBREM-812 URL: http://jira.jboss.com/jira/browse/JBREM-812 Project: JBoss Remoting Issue Type: Task Security Level: Public (Everyone can see) Components: r3 api Reporter: David Lloyd Assigned To: David Lloyd Priority: Minor Fix For: 3.0.0.Alpha1 (Otter) The Remoting 3 API presently has a mechanism to discover endpoints and supply information about how to connect to discovered endpoints. A mechanism is also needed to allow a user to find any endpoint that provides a specific service. This mechanism would preferably work in tandem with the existing discovery API. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

17 years, 11 months

1
5
0 / 0

[JBoss JIRA] Created: (JBCACHE-1141) Redesign evictions for greater flexibility

by Manik Surtani (JIRA)

Redesign evictions for greater flexibility ------------------------------------------ Key: JBCACHE-1141 URL: http://jira.jboss.com/jira/browse/JBCACHE-1141 Project: JBoss Cache Issue Type: Feature Request Security Level: Public (Everyone can see) Components: Eviction Reporter: Manik Surtani Assigned To: Manik Surtani Fix For: 3.x -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

17 years, 11 months

2
6
0 / 0

[JBoss JIRA] Created: (JBCACHE-941) org.jboss.cache.Caches, which allows for users to access a Cache using various collection interfaces

by Elias Ross (JIRA)

org.jboss.cache.Caches, which allows for users to access a Cache using various collection interfaces ---------------------------------------------------------------------------------------------------- Key: JBCACHE-941 URL: http://jira.jboss.com/jira/browse/JBCACHE-941 Project: JBoss Cache Issue Type: Feature Request Security Level: Public (Everyone can see) Reporter: Elias Ross Assigned To: Manik Surtani The java.util.Collections utility class supplies useful methods for dealing with legacy interfaces and wrapping collection classes for concurrency, type safety, read-only, etc. In a simiilar vein, I wrote a "Caches" class that returns java.util.Map instances for a Node, which allow data to be modified through the standard Map interface. This I expect to be extremely useful for allowing uses to integrate their existing application with JBoss Cache, and will eliminate some of the confusion of using a new API and they can use the API they know best. Users also often demand an API which is "generic" so that their code is not tied to a particular vendor. There are basically two methods in Caches, one looks like this: Cache cache = DefaultCacheFactory.getInstance().createCache(); Map m = Caches.asMap(cache); m.put("foo", "bar"); The API and examples explain themselves. "Caches" could also include other useful methods for printing or reporting. Note that this functionality could be considered duplicated from PojoCache...) -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

17 years, 11 months

3
13
0 / 0

[JBoss JIRA] Created: (JBCACHE-1250) Add a Node.clearChildren() functionality

by Brian Stansberry (JIRA)

Add a Node.clearChildren() functionality ---------------------------------------- Key: JBCACHE-1250 URL: http://jira.jboss.com/jira/browse/JBCACHE-1250 Project: JBoss Cache Issue Type: Feature Request Security Level: Public (Everyone can see) Reporter: Brian Stansberry Assigned To: Manik Surtani For next major API change. Equivalent to Node.clearData(), but removes the children. Use case is trying to atomically remove everything under some structural node, while leaving the structural node in place. The best that can be done now is either: 1) Remove the node and re-add it, but this doesn't work for remote caches with INVALIDATION, since both the removal and the addition propagate as invalidation messages. Remote caches are left w/o the structural node. Plus it's not atomic. 2) Query for the children and remove them one by one. Also not atomic, plus if lockParentForChildInsertRemove is false you have to deal with other threads possibly adding new children while you are removing. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

17 years, 11 months

2
9
0 / 0

[JBoss JIRA] Created: (JBCACHE-789) DelegatingCacheLoader that can use a load balanced proxy

by Brian Stansberry (JIRA)

DelegatingCacheLoader that can use a load balanced proxy -------------------------------------------------------- Key: JBCACHE-789 URL: http://jira.jboss.com/jira/browse/JBCACHE-789 Project: JBoss Cache Issue Type: Feature Request Security Level: Public (Everyone can see) Components: Cache loaders Reporter: Brian Stansberry Assigned To: Brian Stansberry Fix For: 2.2.0 Using cache mode LOCAL and a DelegatingCacheLoader (aka a far-cache) has the potential to be a very performant cluster topology. But, the far cache is a single point of failure. Idea here is to develop an HA proxy to a cluster of far-caches; proxy pins to one far-cache, but can fail over to another if the primary target fails. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

17 years, 11 months

3
9
0 / 0

[JBoss JIRA] Created: (JBCACHE-1262) Refactor TcpCacheServer to use Executor framework

by Manik Surtani (JIRA)

Refactor TcpCacheServer to use Executor framework ------------------------------------------------- Key: JBCACHE-1262 URL: http://jira.jboss.com/jira/browse/JBCACHE-1262 Project: JBoss Cache Issue Type: Feature Request Security Level: Public (Everyone can see) Components: Cache loaders Reporter: Manik Surtani Assigned To: Manik Surtani Fix For: 2.2.0.GA A more robust approach to the current spawning of threads would be to use Java5's executor framework. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

17 years, 11 months

1
2
0 / 0

[JBoss JIRA] Created: (JBCACHE-1259) HA for TCPCacheServer

by Manik Surtani (JIRA)

HA for TCPCacheServer --------------------- Key: JBCACHE-1259 URL: http://jira.jboss.com/jira/browse/JBCACHE-1259 Project: JBoss Cache Issue Type: Feature Request Security Level: Public (Everyone can see) Components: Cache loaders Reporter: Manik Surtani Assigned To: Manik Surtani Fix For: 2.2.0.GA TCPCacheServer needs a HA solution. HA-singleton style approach would work; the TcpCacheLoader needs to be able to handle reconnects though. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

17 years, 11 months

1
2
0 / 0

[JBoss JIRA] Created: (JBCACHE-1015) Notify user (via callback) if application of (async or sync) replication fails

by Bela Ban (JIRA)

Notify user (via callback) if application of (async or sync) replication fails ------------------------------------------------------------------------------ Key: JBCACHE-1015 URL: http://jira.jboss.com/jira/browse/JBCACHE-1015 Project: JBoss Cache Issue Type: Feature Request Security Level: Public (Everyone can see) Reporter: Bela Ban Assigned To: Manik Surtani If a replication cannot be applied (no transactions), then invoke a callback notifying the application, so that some corrective action can be taken -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

17 years, 11 months

2
6
0 / 0

[JBoss JIRA] Created: (JBCACHE-877) TreeCache usage should not depend on trove.jar

by Galder Zamarreno (JIRA)

TreeCache usage should not depend on trove.jar ---------------------------------------------- Key: JBCACHE-877 URL: http://jira.jboss.com/jira/browse/JBCACHE-877 Project: JBoss Cache Issue Type: Bug Security Level: Public (Everyone can see) Affects Versions: 1.4.0.SP1 Reporter: Galder Zamarreno Assigned To: Manik Surtani Priority: Minor A customer is upgrading from JBC 1.1 to 1.4.0.SP1 and even though it only uses plain TreeCache, it gets a NoClassDefFoundError for trove classes. 2006-11-23 13:19:03,781 ERROR RpcDispatcher exception=java.lang.NoClassDefFoundError: gnu/trove/TObjectHashingStrategy This is a TreeCacheAop/PojoCache dependency and therefore, should be isolated and attempted to be loaded only when PojoCache used. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

17 years, 11 months

7
28
0 / 0

2026

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

jboss-jira January 2008