January 2007 - jboss-jira - Jboss List Archives

[JBoss JIRA] Closed: (JBCACHE-546) Move lock related operations to a separate utility, such as NodeLock

by Manik Surtani (JIRA)

[ http://jira.jboss.com/jira/browse/JBCACHE-546?page=all ] Manik Surtani closed JBCACHE-546. --------------------------------- Resolution: Won't Fix There aren't that many methods now, as this has been trimmed quite a bit. A separate class will only make things more confusing since locks are acquired on a per-node basis. > Move lock related operations to a separate utility, such as NodeLock > -------------------------------------------------------------------- > > Key: JBCACHE-546 > URL: http://jira.jboss.com/jira/browse/JBCACHE-546 > Project: JBoss Cache > Issue Type: Sub-task > Security Level: Public(Everyone can see) > Affects Versions: 1.3.0.GA > Reporter: Elias Ross > Assigned To: Manik Surtani > Fix For: 2.0.0.ALPHA2, 2.0.0.GA > > > This is to reduce the amount of methods in Node to keep them fairly succinct. > The lock in a Node itself could be package-protected so that interactions must happen through this class. -- 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

19 years, 4 months

1
0
0 / 0

[JBoss JIRA] Closed: (JBCACHE-543) Consider synchronized(this) instead of a separate lock

by Manik Surtani (JIRA)

[ http://jira.jboss.com/jira/browse/JBCACHE-543?page=all ] Manik Surtani closed JBCACHE-543. --------------------------------- Resolution: Won't Fix > Consider synchronized(this) instead of a separate lock > ------------------------------------------------------ > > Key: JBCACHE-543 > URL: http://jira.jboss.com/jira/browse/JBCACHE-543 > Project: JBoss Cache > Issue Type: Sub-task > Security Level: Public(Everyone can see) > Affects Versions: 1.3.0.GA > Reporter: Elias Ross > Assigned To: Manik Surtani > Fix For: 2.0.0.ALPHA2, 2.0.0.GA > > > This will save one object per node, not a big deal but something. -- 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

19 years, 4 months

1
0
0 / 0

[JBoss JIRA] Closed: (JBCACHE-542) Fix initialization of Node.IdentityLock to actually lazy create

by Manik Surtani (JIRA)

[ http://jira.jboss.com/jira/browse/JBCACHE-542?page=all ] Manik Surtani closed JBCACHE-542. --------------------------------- Resolution: Done > Fix initialization of Node.IdentityLock to actually lazy create > --------------------------------------------------------------- > > Key: JBCACHE-542 > URL: http://jira.jboss.com/jira/browse/JBCACHE-542 > Project: JBoss Cache > Issue Type: Sub-task > Security Level: Public(Everyone can see) > Affects Versions: 1.3.0.GA > Reporter: Elias Ross > Assigned To: Manik Surtani > Fix For: 2.0.0.ALPHA2, 2.0.0.GA > > > Although the JavaDoc says it's lazily created, it's created every time -- 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

19 years, 4 months

1
0
0 / 0

[JBoss JIRA] Closed: (JBCACHE-547) Remove TreeNode and DataNode interfaces

by Manik Surtani (JIRA)

[ http://jira.jboss.com/jira/browse/JBCACHE-547?page=all ] Manik Surtani closed JBCACHE-547. --------------------------------- Resolution: Done These have been refactored > Remove TreeNode and DataNode interfaces > --------------------------------------- > > Key: JBCACHE-547 > URL: http://jira.jboss.com/jira/browse/JBCACHE-547 > Project: JBoss Cache > Issue Type: Sub-task > Security Level: Public(Everyone can see) > Affects Versions: 1.3.0.GA > Reporter: Elias Ross > Assigned To: Manik Surtani > Fix For: 2.0.0.ALPHA2, 2.0.0.GA > > > Possibly both of them to a single, small interface, but keep the method count in the conservative 5-10 method range. -- 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

19 years, 4 months

1
0
0 / 0

[JBoss JIRA] Closed: (JBCACHE-545) Consider removing TreeCache, parent, and name

by Manik Surtani (JIRA)

[ http://jira.jboss.com/jira/browse/JBCACHE-545?page=all ] Manik Surtani closed JBCACHE-545. --------------------------------- Resolution: Done name and parent have been removed. A cache reference is necessary since we now allow calls directly on the node, which means they need to be routed via cache (for the time being) to go through the interceptor stack. Will change in 2.1.0 when we use a proper AOP framework rather than our own handwoven interceptors. > Consider removing TreeCache, parent, and name > --------------------------------------------- > > Key: JBCACHE-545 > URL: http://jira.jboss.com/jira/browse/JBCACHE-545 > Project: JBoss Cache > Issue Type: Sub-task > Security Level: Public(Everyone can see) > Affects Versions: 1.3.0.GA > Reporter: Elias Ross > Assigned To: Manik Surtani > Fix For: 2.0.0.ALPHA2, 2.0.0.GA > > > "name" is redundant with respect to Fqn, which contains the name already > parent can be obtained in O(log(n)) time with a TreeCache instance > TreeCache can be passed in from the user to methods that require it -- 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

19 years, 4 months

1
0
0 / 0

[JBoss JIRA] Created: (JBESB-315) The listener and gateway config files are writtne in the wrong order

by Kevin Conner (JIRA)

The listener and gateway config files are writtne in the wrong order -------------------------------------------------------------------- Key: JBESB-315 URL: http://jira.jboss.com/jira/browse/JBESB-315 Project: JBoss ESB Issue Type: Bug Security Level: Public (Everyone can see) Affects Versions: 4.0 RC1 Reporter: Kevin Conner Assigned To: Kevin Conner Fix For: 4.0 The class responsible for generating the listener and gateway configurations creates the files in the opposite order. -- 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

19 years, 4 months

1
3
0 / 0

[JBoss JIRA] Created: (JBESB-316) Classloader issues on sar redeployment

by Kevin Conner (JIRA)

Classloader issues on sar redeployment -------------------------------------- Key: JBESB-316 URL: http://jira.jboss.com/jira/browse/JBESB-316 Project: JBoss ESB Issue Type: Bug Security Level: Public (Everyone can see) Affects Versions: 4.0 RC1 Reporter: Kevin Conner Assigned To: Kevin Conner Fix For: 4.0 Redeployment of the core services causes the following problems - LinkageError against XMLSerializer - NPEs in AS RepositoryClassLoader The causes are the inclusion of the XML/xerces/xalan jars and the failure to unding the juddi services. -- 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

19 years, 4 months

1
3
0 / 0

[JBoss JIRA] Closed: (JBCACHE-270) Create a notification interceptor

by Manik Surtani (JIRA)

[ http://jira.jboss.com/jira/browse/JBCACHE-270?page=all ] Manik Surtani closed JBCACHE-270. --------------------------------- Fix Version/s: 2.0.0.GA (was: 2.1.0.GA) Resolution: Partially Completed Moved this to 2.0.0, and fixed. You now have 2 ways of emmitting notifications (both via the o.j.c.notifications.Notifier class, obatined via CacheSPI.getNotifier()) - either immediately (causes the Notifier to call callbacks on all registered listeners) or by putting it on a queue. The queue is processed by a notification interceptor, as the invocation leaves the chain (for non-tx calls) or when a tx commits. At the moment though, notifications are still placed on the queue by code in the Cacheimpl, OptimisticNodeInterceptor, OptimisticCreateIfNotExistsInterceptor and CacheLoader/Store interceptors, which isn't ideal, but at least it is a start. > Create a notification interceptor > --------------------------------- > > Key: JBCACHE-270 > URL: http://jira.jboss.com/jira/browse/JBCACHE-270 > Project: JBoss Cache > Issue Type: Feature Request > Security Level: Public(Everyone can see) > Affects Versions: 1.2.4beta > Reporter: Hany Mesha > Assigned To: Manik Surtani > Fix For: 2.0.0.GA > > > The need has arised to create a notification interceptor to handle the callbacks results from different method call events and interceptors emitted events. -- 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

19 years, 4 months

1
0
0 / 0

[JBoss JIRA] Created: (JGRP-399) Make Digest immutable

by Bela Ban (JIRA)

Make Digest immutable --------------------- Key: JGRP-399 URL: http://jira.jboss.com/jira/browse/JGRP-399 Project: JGroups Issue Type: Task Affects Versions: 2.4 Reporter: Bela Ban Assigned To: Bela Ban Fix For: 2.5 - Make Digest immutable - Create MutableDigest (if needed) -- 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

19 years, 4 months

1
1
0 / 0

[JBoss JIRA] Created: (JBESB-295) Add support matrix to release notes

by Mark Little (JIRA)

Add support matrix to release notes ----------------------------------- Key: JBESB-295 URL: http://jira.jboss.com/jira/browse/JBESB-295 Project: JBoss ESB Issue Type: Task Security Level: Public (Everyone can see) Components: Distribution, Documentation Affects Versions: 4.0 RC1 Reporter: Mark Little Assigned To: Mark Little Fix For: 4.0 Define: what databases we support (and for what capabilities/services); what application servers we support; what JDK we support; what registries we support; which version of JBossRules we support. -- 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

19 years, 4 months

1
1
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 2007