January 2007 - jboss-jira - Jboss List Archives

[JBoss JIRA] Created: (JBCACHE-750) PojoCache to deal with POJO without no-arg constructor

by Ben Wang (JIRA)

PojoCache to deal with POJO without no-arg constructor ------------------------------------------------------ Key: JBCACHE-750 URL: http://jira.jboss.com/jira/browse/JBCACHE-750 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 came up from a forum post that uses SynchronizedCollection. Here is the problem that Professor Chiba pointed out: ------ Ben, SynchronizedRandomAccessList class has only the following constructors: static class SynchronizedRandomAccessList<E> extends SynchronizedList<E> implements RandomAccess { SynchronizedRandomAccessList(List<E> list) { super(list); } SynchronizedRandomAccessList(List<E> list, Object mutex) { super(list, mutex); } : } I can modify Javassist so that the above constructors (visible only within the pacakge) will be copied to the generated class. But I am not sure that PojoCache can work with that generated class since it does not have a no-arg constructor. Chiba -------- No easy solution to this problem now. Maybe use the exisiting serialization for once during 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

19 years, 2 months

2
3
0 / 0

[JBoss JIRA] Created: (JBCACHE-947) Optimization in attach and detach; reduce calls to getPojo()

by Elias Ross (JIRA)

Optimization in attach and detach; reduce calls to getPojo() ------------------------------------------------------------ Key: JBCACHE-947 URL: http://jira.jboss.com/jira/browse/JBCACHE-947 Project: JBoss Cache Issue Type: Feature Request Security Level: Public (Everyone can see) Components: PojoCache Affects Versions: PojoCache Reporter: Elias Ross Assigned To: Ben Wang PojoCache.attach() calls getPojo() at least three times. Once in putObjectI() to determine if the existing object is the same as the attaching object (fairly rare condition), then once again in putObjectII() (which might be redundant.) Then, it calls detach() which calls getPojo() -- see below. I believe that simply calling pCache.detach() and returning the old value might be sufficient. Also, detach() likewise locates the object before removal, though the removal method itself returns the original object. This is because notification includes the original object before removal. In some cases, notification may not be required. It may also be better to refactor the notification listener so that every removal doesn't require two calls to "getPojo". I discovered this following the number of calls made in a profiler tool. -- 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, 2 months

2
1
0 / 0

[JBoss JIRA] Created: (JBCACHE-736) PojoCache passivation failure

by Ben Wang (JIRA)

PojoCache passivation failure ----------------------------- Key: JBCACHE-736 URL: http://jira.jboss.com/jira/browse/JBCACHE-736 Project: JBoss Cache Issue Type: Bug Security Level: Public (Everyone can see) Components: PojoCache Affects Versions: 1.4.0 Reporter: Ben Wang Assigned To: Ben Wang In release 1.4 of PojoCache, passivation won't work becuase the new AopEvictionInterceptor and that we override the evict method such that we issue recursiveEvict that in turn is doing _remove(). Becuase of this, it bypasses the passivation interceptor. However, the fix is not so obvious. As it also involves the eviction paradigm for POJo as well. In 2.0 instead, I have opted for not to over-ride evict such that we would only support passivation on a node basis (instead of POJO). This way, passivation is transparent to the POJO level. I have a passivation package to test out these cases. -- 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, 2 months

3
4
0 / 0

[JBoss JIRA] Created: (JBPM-798) Show all instances

by David Lloyd (JIRA)

Show all instances ------------------ Key: JBPM-798 URL: http://jira.jboss.com/jira/browse/JBPM-798 Project: JBoss jBPM Issue Type: Sub-task Reporter: David Lloyd Assigned To: David Lloyd -- 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, 2 months

2
3
0 / 0

[JBoss JIRA] Created: (JBPM-762) show processdefinition.xml in web console

by Tom Baeyens (JIRA)

show processdefinition.xml in web console ----------------------------------------- Key: JBPM-762 URL: http://jira.jboss.com/jira/browse/JBPM-762 Project: JBoss jBPM Issue Type: Feature Request Components: Web Interface Reporter: Tom Baeyens Assigned To: Tom Baeyens Priority: Minor Since 3.1.3 (now in branch_3_1) and 3.2.Alpha2 (now in HEAD), the processdefinition.xml file will be available as a binary file attachment to the process. See also JBPM-617 It would be great if admins could request to see the XML for a given process definition. Preferrably with syntax coloring. But i couldn't yet find a good XSLT template that handles HTML rendering of an XML file. -- 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, 2 months

3
4
0 / 0

[JBoss JIRA] Created: (JBPM-804) Move a token

by David Lloyd (JIRA)

Move a token ------------ Key: JBPM-804 URL: http://jira.jboss.com/jira/browse/JBPM-804 Project: JBoss jBPM Issue Type: Sub-task Reporter: David Lloyd Assigned To: David Lloyd -- 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, 2 months

2
3
0 / 0

[JBoss JIRA] Created: (JBPM-805) List all process instance tokens

by David Lloyd (JIRA)

List all process instance tokens -------------------------------- Key: JBPM-805 URL: http://jira.jboss.com/jira/browse/JBPM-805 Project: JBoss jBPM Issue Type: Sub-task Reporter: David Lloyd Assigned To: David Lloyd -- 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, 2 months

2
3
0 / 0

[JBoss JIRA] Created: (JBPM-800) Show process instance history

by David Lloyd (JIRA)

Show process instance history ----------------------------- Key: JBPM-800 URL: http://jira.jboss.com/jira/browse/JBPM-800 Project: JBoss jBPM Issue Type: Sub-task Reporter: David Lloyd Assigned To: David Lloyd -- 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, 2 months

2
3
0 / 0

[JBoss JIRA] Created: (JBPM-802) Cancel tokens

by David Lloyd (JIRA)

Cancel tokens ------------- Key: JBPM-802 URL: http://jira.jboss.com/jira/browse/JBPM-802 Project: JBoss jBPM Issue Type: Sub-task Reporter: David Lloyd Assigned To: David Lloyd -- 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, 2 months

2
3
0 / 0

[JBoss JIRA] Created: (JBPM-795) Webapp won't display box on process diagram for non-task nodes

by David Lloyd (JIRA)

Webapp won't display box on process diagram for non-task nodes -------------------------------------------------------------- Key: JBPM-795 URL: http://jira.jboss.com/jira/browse/JBPM-795 Project: JBoss jBPM Issue Type: Bug Components: Web Interface Affects Versions: jBPM 3.2 alpha 1, jBPM 3.2 alpha 2 Reporter: David Lloyd Assigned To: Tom Baeyens Priority: Minor If the current node is not a task node (in other words, it's a start node like in the websale example), the box won't render. -- 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, 2 months

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