July 2006 - jboss-jira - Jboss List Archives

[JBoss JIRA] Resolved: (JBCACHE-108) Make CacheLoader use SPI rather than TreeCache implementation

by Manik Surtani (JIRA)

[ http://jira.jboss.com/jira/browse/JBCACHE-108?page=all ] Manik Surtani resolved JBCACHE-108. ----------------------------------- Resolution: Done > Make CacheLoader use SPI rather than TreeCache implementation > ------------------------------------------------------------- > > Key: JBCACHE-108 > URL: http://jira.jboss.com/jira/browse/JBCACHE-108 > Project: JBoss Cache > Issue Type: Sub-task > Reporter: Bela Ban > Assigned To: Manik Surtani > Fix For: 2.0.0 > > -- 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

20 years

1
0
0 / 0

[JBoss JIRA] Closed: (JBCACHE-595) Merge API interfaces

by Manik Surtani (JIRA)

[ http://jira.jboss.com/jira/browse/JBCACHE-595?page=all ] Manik Surtani closed JBCACHE-595. --------------------------------- Resolution: Done > Merge API interfaces > -------------------- > > Key: JBCACHE-595 > URL: http://jira.jboss.com/jira/browse/JBCACHE-595 > Project: JBoss Cache > Issue Type: Task > Security Level: Public(Everyone can see) > Affects Versions: 1.3.0.SP1 > Reporter: Manik Surtani > Assigned To: Manik Surtani > Priority: Blocker > Fix For: 2.0.0 > > Time Spent: 30 minutes > Remaining Estimate: 0 minutes > > * Merge TreeCacheListener, EnhancedTreeCacheListener, add an API to pass in data > * Merge CacheLoader + ExtendedCacheLoader -- 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

20 years

1
0
0 / 0

[JBoss JIRA] Closed: (JBCACHE-301) putIfAbsent(), putIfNull(), putIfEquals() etc

by Manik Surtani (JIRA)

[ http://jira.jboss.com/jira/browse/JBCACHE-301?page=all ] Manik Surtani closed JBCACHE-301. --------------------------------- Resolution: Done > putIfAbsent(), putIfNull(), putIfEquals() etc > --------------------------------------------- > > Key: JBCACHE-301 > URL: http://jira.jboss.com/jira/browse/JBCACHE-301 > Project: JBoss Cache > Issue Type: Feature Request > Security Level: Public(Everyone can see) > Reporter: Bela Ban > Assigned To: Manik Surtani > Fix For: 2.0.0 > > > atomic operations, this can avoid code like > Object o=cache.get(FQN, KEY); > if(o != null && COND.equals(o)) { > cache.put(FQN, KEY, myObj); > } > This is replaced with cache.putIfEquals(FQN, KEY, COND, myObj); > Another example: > if(!cache.exists(FQN, KEY)) > cache.put(FQN, KEY, VAL); > can be replaced with > cache.putIfAbsent(FQN, KEY, VAL) -- 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

20 years

1
0
0 / 0

[JBoss JIRA] Commented: (JBCACHE-301) putIfAbsent(), putIfNull(), putIfEquals() etc

by Manik Surtani (JIRA)

[ http://jira.jboss.com/jira/browse/JBCACHE-301?page=comments#action_12339777 ] Manik Surtani commented on JBCACHE-301: --------------------------------------- putIfNull() implemented. Limited use for other such helpers, such as putIfEquals()? > putIfAbsent(), putIfNull(), putIfEquals() etc > --------------------------------------------- > > Key: JBCACHE-301 > URL: http://jira.jboss.com/jira/browse/JBCACHE-301 > Project: JBoss Cache > Issue Type: Feature Request > Security Level: Public(Everyone can see) > Reporter: Bela Ban > Assigned To: Manik Surtani > Fix For: 2.0.0 > > > atomic operations, this can avoid code like > Object o=cache.get(FQN, KEY); > if(o != null && COND.equals(o)) { > cache.put(FQN, KEY, myObj); > } > This is replaced with cache.putIfEquals(FQN, KEY, COND, myObj); > Another example: > if(!cache.exists(FQN, KEY)) > cache.put(FQN, KEY, VAL); > can be replaced with > cache.putIfAbsent(FQN, KEY, VAL) -- 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

20 years

1
0
0 / 0

[JBoss JIRA] Created: (JBRULES-376) Add Java code completion for consequences, eval and functions

by Kris Verlaenen (JIRA)

Add Java code completion for consequences, eval and functions ------------------------------------------------------------- Key: JBRULES-376 URL: http://jira.jboss.com/jira/browse/JBRULES-376 Project: JBoss Rules Issue Type: Feature Request Security Level: Public (Everyone can see) Components: Eclipse IDE Reporter: Kris Verlaenen Assigned To: Kris Verlaenen Fix For: 3.0.3 The DRL editor should offer standard Java code completion for consequences, eval and functions. This should support all variables known at that point (i.e. rule conditions variables or function parameters). -- 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

20 years

2
1
0 / 0

[JBoss JIRA] Resolved: (JBPORTAL-450) Implement mappings of WSRP engine failure, portlet failures to WSRP

by Chris Laprun (JIRA)

[ http://jira.jboss.com/jira/browse/JBPORTAL-450?page=all ] Chris Laprun resolved JBPORTAL-450. ----------------------------------- Resolution: Done Assignee: Chris Laprun > Implement mappings of WSRP engine failure, portlet failures to WSRP > ------------------------------------------------------------------- > > Key: JBPORTAL-450 > URL: http://jira.jboss.com/jira/browse/JBPORTAL-450 > Project: JBoss Portal > Issue Type: Sub-task > Security Level: Public(Everyone can see) > Components: Portal WSRP > Affects Versions: 2.4 Final > Reporter: Polina Alber > Assigned To: Chris Laprun > Fix For: 2.4 Final > > Original Estimate: 4 days > Remaining Estimate: 4 days > -- 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

20 years

1
0
0 / 0

[JBoss JIRA] Assigned: (JBPORTAL-453) Implement producer URL rewriting

by Chris Laprun (JIRA)

[ http://jira.jboss.com/jira/browse/JBPORTAL-453?page=all ] Chris Laprun reassigned JBPORTAL-453: ------------------------------------- Assignee: Chris Laprun (was: Julien Viet) > Implement producer URL rewriting > -------------------------------- > > Key: JBPORTAL-453 > URL: http://jira.jboss.com/jira/browse/JBPORTAL-453 > Project: JBoss Portal > Issue Type: Sub-task > Security Level: Public(Everyone can see) > Components: Portal WSRP > Affects Versions: 2.4 Final, 2.6 Final > Reporter: Polina Alber > Assigned To: Chris Laprun > Fix For: 2.6 Final > > Original Estimate: 1 week > Remaining Estimate: 1 week > -- 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

20 years

1
0
0 / 0

[JBoss JIRA] Updated: (JBPORTAL-283) WSRP producer

by Chris Laprun (JIRA)

[ http://jira.jboss.com/jira/browse/JBPORTAL-283?page=all ] Chris Laprun updated JBPORTAL-283: ---------------------------------- Fix Version/s: 2.6 Final (was: 2.4 Final) > WSRP producer > ------------- > > Key: JBPORTAL-283 > URL: http://jira.jboss.com/jira/browse/JBPORTAL-283 > Project: JBoss Portal > Issue Type: Feature Request > Security Level: Public(Everyone can see) > Components: Portal WSRP > Affects Versions: 2.2 Final > Reporter: Julien Viet > Assigned To: Chris Laprun > Fix For: 2.6 Final > > > Compliant implementation of WSRP producer. -- 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

20 years

1
0
0 / 0

[JBoss JIRA] Assigned: (JBPORTAL-283) WSRP producer

by Chris Laprun (JIRA)

[ http://jira.jboss.com/jira/browse/JBPORTAL-283?page=all ] Chris Laprun reassigned JBPORTAL-283: ------------------------------------- Assignee: Chris Laprun > WSRP producer > ------------- > > Key: JBPORTAL-283 > URL: http://jira.jboss.com/jira/browse/JBPORTAL-283 > Project: JBoss Portal > Issue Type: Feature Request > Security Level: Public(Everyone can see) > Components: Portal WSRP > Affects Versions: 2.2 Final > Reporter: Julien Viet > Assigned To: Chris Laprun > Fix For: 2.4 Final > > > Compliant implementation of WSRP producer. -- 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

20 years

1
0
0 / 0

[JBoss JIRA] Created: (JBPORTAL-958) Make sure that portlet buttons are always in the same order

by Chris Laprun (JIRA)

Make sure that portlet buttons are always in the same order ----------------------------------------------------------- Key: JBPORTAL-958 URL: http://jira.jboss.com/jira/browse/JBPORTAL-958 Project: JBoss Portal Issue Type: Feature Request Security Level: Public (Everyone can see) Components: Portal Portlet Affects Versions: 2.4 Final Reporter: Chris Laprun Assigned To: Chris Laprun Priority: Minor Fix For: 2.4 Final For example, when a portlet is in normal window state, the maximize button is on the far right while the minize one is on the left of the maximize one. When the portlet is maximized, the normal button is on the left of the minimize button which is then at the far right of the title bar. -- 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

20 years

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 July 2006