July 2006 - jboss-jira - Jboss List Archives

[JBoss JIRA] Created: (JBCACHE-707) PojoCache to aspectize JDom classes

by Ben Wang (JIRA)

PojoCache to aspectize JDom classes ----------------------------------- Key: JBCACHE-707 URL: http://jira.jboss.com/jira/browse/JBCACHE-707 Project: JBoss Cache Issue Type: Task Security Level: Public (Everyone can see) Components: PojoCache Reporter: Ben Wang Assigned To: Ben Wang Fix For: POJOCache This is suggested by Bela during a customer visit. Idea is the customer is using JDom internally to store the documents such as mail, fax, email, parcel, and the like. However, for clustering purpose, each single update on document element would require replication of the whole document. Not a very efficient process. If PojoCache can aspectize JDom classes then fine-grained replication can be done transparently. -- 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, 7 months

3
13
0 / 0

[JBoss JIRA] Created: (JBCACHE-712) PojoCache needs a new tutorial gui

by Ben Wang (JIRA)

PojoCache needs a new tutorial gui ---------------------------------- Key: JBCACHE-712 URL: http://jira.jboss.com/jira/browse/JBCACHE-712 Project: JBoss Cache Issue Type: Feature Request Security Level: Public (Everyone can see) Components: PojoCache Reporter: Ben Wang Assigned To: Ben Wang Fix For: 2.0.0 Currently, the gui for PojoCache just display the internal cache node straight out so user can observe the field-level change. This however may not work under 2.0 since the internal ojbect model has changed. One possiblity is the user will have to inspect the internal area as well (that is clouded by a random GUID though). The other one is we add intelligence to the GUI such that display is for object view. This can relate to the CacheIDE as well. -- 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, 8 months

2
4
0 / 0

[JBoss JIRA] Created: (JBCACHE-719) Update PojoCache unit test and examples with a proper id

by Ben Wang (JIRA)

Update PojoCache unit test and examples with a proper id -------------------------------------------------------- Key: JBCACHE-719 URL: http://jira.jboss.com/jira/browse/JBCACHE-719 Project: JBoss Cache Issue Type: Task Security Level: Public (Everyone can see) Components: PojoCache Reporter: Ben Wang Assigned To: Ben Wang Fix For: 2.0.0 Currently, in both the unit tests and examples for PojoCache, we all use some sort of fqn, e.g, "/test/1". A better semantics should be just "test" or "test/1" (without leading slash). -- 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, 8 months

3
3
0 / 0

[JBoss JIRA] Created: (JBCACHE-698) PojoCache Collection Map when detached has the in-memory copy in reverse order

by Ben Wang (JIRA)

PojoCache Collection Map when detached has the in-memory copy in reverse order ------------------------------------------------------------------------------ Key: JBCACHE-698 URL: http://jira.jboss.com/jira/browse/JBCACHE-698 Project: JBoss Cache Issue Type: Bug Security Level: Public (Everyone can see) Components: PojoCache Reporter: Ben Wang Assigned To: Ben Wang Fix For: POJOCache say, we do, cache.attach("test", map); origMap = cache.detach("test"); origMap would have the (key, value) pair in reverse 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

16 years, 8 months

2
3
0 / 0

[JBoss JIRA] Created: (JBCACHE-697) PojoCache Collection sub-field when detached will revert back to the original reference

by Ben Wang (JIRA)

PojoCache Collection sub-field when detached will revert back to the original reference --------------------------------------------------------------------------------------- Key: JBCACHE-697 URL: http://jira.jboss.com/jira/browse/JBCACHE-697 Project: JBoss Cache Issue Type: Feature Request Security Level: Public (Everyone can see) Components: PojoCache Reporter: Ben Wang Assigned To: Ben Wang Fix For: POJOCache In PojoCache 1.4, when a Pojo has a Collection sub-object, it will dynamically replace the reference with a corresponding ClassProxy one such that we can intercept the Collection APIs. This is in attached state. When the POJO is detached, we would simply keep the ClassProxy reference but rather point the interceptor to the original reference. This works fine except when the POJO is meant for remoting as ClassProxy is not Serializable and not for direct manipulation. The solution is when a POJO is detached, it will dynamically swap back the original reference and discard the ClassProxy. This way, it is semantically similar to a regular POJO as well. There will be no issue of Remoting, as an example. -- 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, 8 months

2
5
0 / 0

[JBoss JIRA] Created: (JBPM-691) Decision class does not allow setting of Decision Delegation

by Chris OBrien (JIRA)

Decision class does not allow setting of Decision Delegation ------------------------------------------------------------ Key: JBPM-691 URL: http://jira.jboss.com/jira/browse/JBPM-691 Project: JBoss jBPM Issue Type: Feature Request Components: Core Engine Affects Versions: jBPM 3.1.1 Environment: Windows XP MySQL WSAD 5.1.2 Reporter: Chris OBrien Assigned To: Tom Baeyens In programmatically creating/manipulating a process definition, one cannot specify a Decision Delegation on a Decision node. The Decision class just needs a method like: public void setDecisionDelegation( Delegation del ) { this.decisionDelegation = del; } I have added this to my install, and it allows me to programmatically change the process definition to define the handler. -- 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, 8 months

4
4
0 / 0

[JBoss JIRA] Created: (BPEL-200) Redeployment of a changed PAR (with modified .bpel) requires App Server Restart

by Burr Sutter (JIRA)

Redeployment of a changed PAR (with modified .bpel) requires App Server Restart ------------------------------------------------------------------------------- Key: BPEL-200 URL: http://jira.jboss.com/jira/browse/BPEL-200 Project: JBoss jBPM BPEL Issue Type: Bug Security Level: Public (Everyone can see) Components: Engine Affects Versions: jBPM BPEL 1.1 beta 1 Environment: JBoss 4.0.4.GA with EJB3 using beta JEMS installer Reporter: Burr Sutter Assigned To: Alejandro Guizar Simply modifying the .bpel script, running pack-definition and deploy-definition do not reload/restart the process (even though all process instances have terminated). The only thing I've found that refreshes the BPEL engine properly is to restart the App Server. -- 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, 8 months

3
6
0 / 0

[JBoss JIRA] Created: (JBCACHE-708) EOF exception in TcpCacheLoader

by Manik Surtani (JIRA)

EOF exception in TcpCacheLoader ------------------------------- Key: JBCACHE-708 URL: http://jira.jboss.com/jira/browse/JBCACHE-708 Project: JBoss Cache Issue Type: Bug Security Level: Public (Everyone can see) Components: Cache loaders Affects Versions: 1.4.0 Reporter: Manik Surtani Assigned To: Manik Surtani Fix For: 2.0.0 Happens when a node in the cluster dies. See last few postings in forum thread for details. -- 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, 9 months

2
3
0 / 0

[JBoss JIRA] Created: (JBCACHE-710) CacheLoader passivation/activation produces recursive exception when loader.remove fails

by Ben Wang (JIRA)

CacheLoader passivation/activation produces recursive exception when loader.remove fails ---------------------------------------------------------------------------------------- Key: JBCACHE-710 URL: http://jira.jboss.com/jira/browse/JBCACHE-710 Project: JBoss Cache Issue Type: Bug Security Level: Public (Everyone can see) Components: Cache loaders Affects Versions: 1.4.0 Reporter: Ben Wang Assigned To: Manik Surtani Priority: Critical Fix For: 2.0.0 I have encountered this problem during ejb3 sfsb port of JBC1.4. This is what happened: In ActivationInterceptor.java, we have: if (n != null && !n.containsKey(TreeCache.UNINITIALIZED)) { if (n.hasChildren()) { if (allInitialized(n)) { log.debug("children all initialized"); remove(fqn); } } else if (loaderNoChildren(fqn)) { log.debug("no children " + n); remove(fqn); } } } } return retval; } private void remove(Fqn fqn) throws Exception { loader.remove(fqn); cache.notifyNodeActivate(fqn, false); if (cache.getUseInterceptorMbeans()&& statsEnabled) m_activations++; } problem arises when loader.remove(fqn) fails (can be a file lock there, e.g.), then if I have a Cache listener to receive nodeActivate event, and in there, I will have to retrieve the node value, e.g., cache.get(fqn, key) to process some logic, then get(fqn, key) will come back to ActivationInterceptor and attempt another .remove() and therefore the recursion. A proposed fix is we should throw exception when removing the node fails in CacheLoader (I am using FileCacheLoader), e.g., DataNotRemovedException. That way, ActivationInterceptor can catch it here and skip event notification (since it won't be valid anyway). -- 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, 9 months

4
10
0 / 0

[JBoss JIRA] Created: (JBCACHE-723) Proper collection rollback

by Ben Wang (JIRA)

Proper collection rollback -------------------------- Key: JBCACHE-723 URL: http://jira.jboss.com/jira/browse/JBCACHE-723 Project: JBoss Cache Issue Type: Sub-task Security Level: Public (Everyone can see) Components: PojoCache Reporter: Ben Wang Assigned To: Ben Wang Fix For: 2.0.0 It is not properly yet via the undointerceptor -- 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, 9 months

2
3
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

jboss-jira July 2006