July 2008 - jboss-jira - Jboss List Archives

[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

16 years, 2 months

2
9
0 / 0

[JBoss JIRA] Created: (JBDEPLOY-66) Simplify the StructureDeployer api

by Adrian Brock (JIRA)

Simplify the StructureDeployer api ---------------------------------- Key: JBDEPLOY-66 URL: https://jira.jboss.org/jira/browse/JBDEPLOY-66 Project: JBoss Deployers Issue Type: Task Components: structure Reporter: Adrian Brock Fix For: JBDEPLOY-2.0.0.CR1 Currently the StructureDeployer api has a horrible method signature: boolean determineStructure(VirtualFile root, VirtualFile parent, VirtualFile file, StructureMetaData metaData, VFSStructuralDeployers deployers) throws DeploymentException; These are fairly ad hoc and difficult to change when we need to pass new context. We should introduce a new class "StructureContext" which encapsulates these parameters and any future parameters. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

16 years, 2 months

1
1
0 / 0

[JBoss JIRA] Created: (JBAS-5409) Redesign Remoting Aspect

by Andrew Lee Rubinger (JIRA)

Redesign Remoting Aspect ------------------------ Key: JBAS-5409 URL: http://jira.jboss.com/jira/browse/JBAS-5409 Project: JBoss Application Server Issue Type: Task Security Level: Public (Everyone can see) Reporter: Andrew Lee Rubinger Assigned To: Dimitris Andreadis Remoting aspect has a dependency on Tx and Security Aspects -- 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

16 years, 2 months

2
4
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

16 years, 2 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

16 years, 2 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

16 years, 2 months

1
2
0 / 0

[JBoss JIRA] Created: (JBCACHE-1308) Genericize getData() Map returned by notication events

by Brian Stansberry (JIRA)

Genericize getData() Map returned by notication events ------------------------------------------------------ Key: JBCACHE-1308 URL: http://jira.jboss.com/jira/browse/JBCACHE-1308 Project: JBoss Cache Issue Type: Feature Request Security Level: Public (Everyone can see) Affects Versions: 2.1.0.GA Reporter: Brian Stansberry Assigned To: Manik Surtani Priority: Minor The Map returned by getData() in the various notification events is not genericized. AFAICT it should use the same <K, V> as the Cache<K, V> that emits the events. Relevant event classes are NodeActivatedEvent, NodeLoadedEvent, NodeModifiedEvent, NodePassivatedEvent. -- 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

16 years, 2 months

2
3
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

16 years, 2 months

2
6
0 / 0

[JBoss JIRA] Created: (JBAS-5747) Upgrade to the latest JSF implementation 1.2_09 (from 1.2_08)

by Carsten Hoehne (JIRA)

Upgrade to the latest JSF implementation 1.2_09 (from 1.2_08) ------------------------------------------------------------- Key: JBAS-5747 URL: http://jira.jboss.com/jira/browse/JBAS-5747 Project: JBoss Application Server Issue Type: Sub-task Security Level: Public (Everyone can see) Affects Versions: JBossAS-5.0.0.CR1 Reporter: Carsten Hoehne Fix For: JBossAS-5.0.0.CR2 Please have a look here: http://www.jboss.org/file-access/default/members/jbossrichfaces/freezone/... There seems to be a bug in 1.2_08 So it has to be upgraded. -- 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

16 years, 2 months

4
7
0 / 0

[JBoss JIRA] Created: (JBRULES-1702) BRMS: uploading a decision table breaks the package

by Jaroslaw Kijanowski (JIRA)

BRMS: uploading a decision table breaks the package --------------------------------------------------- Key: JBRULES-1702 URL: https://jira.jboss.org/jira/browse/JBRULES-1702 Project: JBoss Drools Issue Type: Bug Security Level: Public (Everyone can see) Components: drools-brms Affects Versions: 5.0.0.M1 Reporter: Jaroslaw Kijanowski Assignee: Michael Neale Fix For: 5.0.0.M2 I create a rule, then upload a decision table (see attached) and: - if I compile the package it looks good, however it isn't, I cannot run a test scenario for example, because I will get missing imports of facts from the first rule; - if I create another rule, I won't be able to compile the package due to missing imports; I guess the reason for this is that the decision table adds its own import and package statements in the middle of the rule file. Here's the source of the package with one "regular" rule and one rule coming from the decision table: package myNewPAckage import com.model.Person import com.model.Alarm import com.model.Message rule "first" dialect "mvel" when Alarm( ) then Person fact0 = new Person(); fact0.setAge( 18 ); insert( fact0 ); end package XLSRules; #generated from Decision Table import com.model.Message; #From row number: 11 rule "HelloWorld_11" when m:Message(status == Message.HELLO) then System.out.println(m.getMessage()); m.setMessage("Goodbye cruel world");update(m); m.setStatus(Message.GOODBYE);update(m); end #From row number: 12 rule "HelloWorld_12" when m:Message(status == Message.GOODBYE) then System.out.println(m.getMessage()); end -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

16 years, 2 months

2
9
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

jboss-jira July 2008