November 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

18 years, 10 months

3
13
0 / 0

[JBoss JIRA] Created: (JBCACHE-727) PojoCache to create an impl for Iterator interface

by Ben Wang (JIRA)

PojoCache to create an impl for Iterator interface -------------------------------------------------- Key: JBCACHE-727 URL: http://jira.jboss.com/jira/browse/JBCACHE-727 Project: JBoss Cache Issue Type: Task Security Level: Public (Everyone can see) Components: PojoCache Reporter: Ben Wang Assigned To: Ben Wang Fix For: POJOCache Currently we have proxy impl for Collection classes and the iterator is implemented as inner class. We may need a default Iterator impl as well so when user is doing like, setIterator(Iterator it) we can replace it with our own (such that we can intercept 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

18 years, 10 months

2
3
0 / 0

[JBoss JIRA] Created: (JBCACHE-726) PojoCache to replicate static field variable

by Ben Wang (JIRA)

PojoCache to replicate static field variable -------------------------------------------- Key: JBCACHE-726 URL: http://jira.jboss.com/jira/browse/JBCACHE-726 Project: JBoss Cache Issue Type: Feature Request Security Level: Public (Everyone can see) Components: PojoCache Reporter: Ben Wang Assigned To: Ben Wang Priority: Minor Fix For: POJOCache There may be use cases that staic field variable is not final nor constant. In this case, can we replicate that field? The problem is static variable is global scoped, so where should we store it under? Maybe a separate area for global space, but this will break BR, btw. -- 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

18 years, 10 months

2
11
0 / 0

[JBoss JIRA] Created: (JBCACHE-737) PojoCache to handle Java array

by Ben Wang (JIRA)

PojoCache to handle Java array ------------------------------ Key: JBCACHE-737 URL: http://jira.jboss.com/jira/browse/JBCACHE-737 Project: JBoss Cache Issue Type: Task Security Level: Public (Everyone can see) Components: PojoCache Reporter: Ben Wang Assigned To: Ben Wang Fix For: POJOCache Currently we depend on JBoss Aop to handle interception. However, it currently doesn't handle Java array, e.g., pojo[]. We will need this at least to do corase-grained replication. -- 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

18 years, 10 months

2
4
0 / 0

[JBoss JIRA] Created: (JBCACHE-732) PojoCache introduces @NonTransient annotation

by Ben Wang (JIRA)

PojoCache introduces @NonTransient annotation --------------------------------------------- Key: JBCACHE-732 URL: http://jira.jboss.com/jira/browse/JBCACHE-732 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 We need to introduce a @NonTransient annotation to override the transient modifier. -- 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

18 years, 10 months

2
5
0 / 0

[JBoss JIRA] Created: (JBPM-756) log.debug calls are unprotected

by Dave Caruana (JIRA)

log.debug calls are unprotected ------------------------------- Key: JBPM-756 URL: http://jira.jboss.com/jira/browse/JBPM-756 Project: JBoss jBPM Issue Type: Bug Components: Core Engine Affects Versions: jBPM 3.1.2 Environment: Window XP, Java 5 Reporter: Dave Caruana Assigned To: Tom Baeyens Within org.jbpm.context.exe.VariableContainer there are calls to log.debug. In particular: line 156: log.debug("create variable '"+name+"' in '"+this+"' with value '"+value+"'"); line 160: log.debug("update variable '"+name+"' in '"+this+"' to value '"+value+"'"); However, they are unprotected i.e. the method is called even if debug logging is not switched on. This is not too much of a problem if the variable value is of a primitive type, but sometimes, values can be complex (including their toString()). "if (log.isDebugEnabled())" statements are missing. -- 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

18 years, 10 months

3
6
0 / 0

[JBoss JIRA] Created: (JBCACHE-770) PojoCache to support non-serializable and no-aspectized POJO

by Ben Wang (JIRA)

PojoCache to support non-serializable and no-aspectized POJO ------------------------------------------------------------ Key: JBCACHE-770 URL: http://jira.jboss.com/jira/browse/JBCACHE-770 Project: JBoss Cache Issue Type: Task Security Level: Public (Everyone can see) Components: PojoCache Reporter: Ben Wang Assigned To: Ben Wang Priority: Minor Fix For: PojoCache Currently in 2.0, we have to drop the support for the non-serializable and non-aspectized POJO, that is, a POJO that is neither implements Serializable or instrumented. -- 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

18 years, 10 months

2
3
0 / 0

[JBoss JIRA] Created: (JBCACHE-835) PojoCache need merge api?

by Ben Wang (JIRA)

PojoCache need merge api? ------------------------- Key: JBCACHE-835 URL: http://jira.jboss.com/jira/browse/JBCACHE-835 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 Currently, PojoCache attach api will override the current pojo in the cache. It doesn't really have a merge functionality. Question is do we really need to have a merge api? The following is the spec for the ejb3 entity manager merge api. However, the ejb3 em api doesn't quite apply in the case of PojoCache. You can see the object identity is by PK instead of reference. So during merge, a copy of Pojo is created instead. The TravelAgentBean.updateCabin() method takes its cabin parameter and merges it back into the current persistence context of the entity manager by calling the merge() operation: @PersistenceContext EntityManager entityManager; @TransactionAttribute(REQUIRED) public void updateCabin(Cabin cabin) { Cabin copy = entityManager.merge(cabin); } The changes made by the remote Swing client will now be reflected in persistence storage when the entity manager decides to flush to the database. The following rules apply when merging in the cabin parameter of the updateCabin() method: • If the entity manager isn't already managing a Cabin instance with the same ID, a full copy of the parameter is made and returned from the merge() method. This copy is managed by the entity manager, and any additional setter methods called on this copy will be synchronized with the database when the EntityManager decides to flush. The cabin parameter remains detached and unmanaged. • If the entity manager is already managing a Cabin instance with the same primary key, then the contents of the parameter are copied into this managed object instance. The merge() operation will return this managed instance. The cabin parameter remains detached and unmanaged. -- 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

18 years, 10 months

2
2
0 / 0

[JBoss JIRA] Created: (JBCACHE-791) PojoCache to revisit implementation for get/put Options

by Ben Wang (JIRA)

PojoCache to revisit implementation for get/put Options ------------------------------------------------------- Key: JBCACHE-791 URL: http://jira.jboss.com/jira/browse/JBCACHE-791 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 During the initial implementation of PojoCache, we have to disable the Option API like supressLocking, etc in InternaHelper. We need to revisit them to make sure they are performant. -- 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

18 years, 10 months

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

18 years, 10 months

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