May 2007 - jboss-jira - Jboss List Archives

[JBoss JIRA] Created: (EJBTHREE-809) Update online documentation

by William DeCoste (JIRA)

Update online documentation --------------------------- Key: EJBTHREE-809 URL: http://jira.jboss.com/jira/browse/EJBTHREE-809 Project: EJB 3.0 Issue Type: Task Affects Versions: EJB 3.0 RC9 - Patch 1 Reporter: William DeCoste Assigned To: William DeCoste Current doc is RC6?? -- 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
5
0 / 0

[JBoss JIRA] Created: (JBMICROCONT-170) Add support for aliases

by Adrian Brock (JIRA)

Add support for aliases ----------------------- Key: JBMICROCONT-170 URL: http://jira.jboss.com/jira/browse/JBMICROCONT-170 Project: JBoss MicroContainer Issue Type: Feature Request Components: Dependency Reporter: Adrian Brock Assigned To: Adrian Brock Fix For: JBossMC_2_0_0_CR1 Add support for aliases to the Microcontainer. This should allow: 1) "static" references known at deployment time which is a generic requirement 2) dynamic references, e.g. when the jmx decorator runs it should add the JMX ObjectName as an alias of the POJO which resolves the issue raised here: http://www.jboss.com/index.html?module=bb&op=viewtopic&t=104814 3) the ObjectName canonical problem from JBMICROCONT-166 where the context gets both the original name and the canonical name -- 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

1
1
0 / 0

[JBoss JIRA] Created: (JGRP-413) Replace separate threads with timer tasks

by Bela Ban (JIRA)

Replace separate threads with timer tasks ----------------------------------------- Key: JGRP-413 URL: http://jira.jboss.com/jira/browse/JGRP-413 Project: JGroups Issue Type: Feature Request Affects Versions: 2.4 Reporter: Bela Ban Assigned To: Bela Ban Fix For: 2.5 E.g. PingWaiter, PingSender -- 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
2
0 / 0

[JBoss JIRA] Created: (JGRP-420) Convert Event.FIND_INITIAL_MBRS to use concurrent stack

by Vladimir Blagojevic (JIRA)

Convert Event.FIND_INITIAL_MBRS to use concurrent stack ------------------------------------------------------- Key: JGRP-420 URL: http://jira.jboss.com/jira/browse/JGRP-420 Project: JGroups Issue Type: Task Affects Versions: 2.5 Reporter: Vladimir Blagojevic Assigned To: Bela Ban Fix For: 2.5 Protocols above PING request initial membership by passing Event.FIND_INITIAL_MBRS down the stack. Prior to concurrent stack this event had to be processed asynchronously since there were deadlock issues - hence the need for PingWaiter. Now, with the concurrent stack, we might possibly eliminate the need for PingWaiter altogether and convert Event.FIND_INITIAL_MBRS to return initial membership as a result. -- 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
2
0 / 0

[JBoss JIRA] Created: (JBRULES-651) JBRMSServiceServlet to log persistent actions

by Michael Neale (JIRA)

JBRMSServiceServlet to log persistent actions --------------------------------------------- Key: JBRULES-651 URL: http://jira.jboss.com/jira/browse/JBRULES-651 Project: JBoss Rules Issue Type: Sub-task Security Level: Public (Everyone can see) Reporter: Michael Neale Assigned To: Michael Neale -- 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
3
0 / 0

[JBoss JIRA] Created: (JBRULES-652) Log viewer to view audit log

by Michael Neale (JIRA)

Log viewer to view audit log ---------------------------- Key: JBRULES-652 URL: http://jira.jboss.com/jira/browse/JBRULES-652 Project: JBoss Rules Issue Type: Sub-task Security Level: Public (Everyone can see) Reporter: Michael Neale Assigned To: Michael Neale -- 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
3
0 / 0

[JBoss JIRA] Created: (JBAOP-378) Repeated instantiation of pojo with per_instance aspects is slow with generated advisors

by Kabir Khan (JIRA)

Repeated instantiation of pojo with per_instance aspects is slow with generated advisors ---------------------------------------------------------------------------------------- Key: JBAOP-378 URL: http://jira.jboss.com/jira/browse/JBAOP-378 Project: JBoss AOP Issue Type: Sub-task Security Level: Public (Everyone can see) Reporter: Kabir Khan Assigned To: Kabir Khan -- 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

1
4
0 / 0

[JBoss JIRA] Created: (JBCACHE-1000) Pojocache tutorial not working

by Rajesh Rajasekaran (JIRA)

Pojocache tutorial not working ------------------------------ Key: JBCACHE-1000 URL: http://jira.jboss.com/jira/browse/JBCACHE-1000 Project: JBoss Cache Issue Type: Bug Security Level: Public (Everyone can see) Components: PojoCache Reporter: Rajesh Rajasekaran Assigned To: Jason T. Greene Fix For: 2.0.0.BETA2 sourceRelative("pojocache.bsh"); loads the cache GUI with the default contents from the script. Trying the set/get methods does not update the GUI. bsh % joe.getAddress().setCity("Taipei"); bsh % ArrayList lang = new ArrayList(); bsh % lang.add("Ensligh"); bsh % lang.add("Mandarin"); bsh % joe.setLanguages(lang); Similar case with pojocacheWithTx.bsh. The cache GUI does not get updated. tx.begin(); addr.setZip(95131); tx.commit(); I tried the tutorials from JBossCache-pojo-2.0.0.BETA1.zip -- 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

4
8
0 / 0

[JBoss JIRA] Created: (JBCACHE-1060) Tutorial - removing a child node from the root still leaves the node in memory

by Galder Zamarreno (JIRA)

Tutorial - removing a child node from the root still leaves the node in memory ------------------------------------------------------------------------------ Key: JBCACHE-1060 URL: http://jira.jboss.com/jira/browse/JBCACHE-1060 Project: JBoss Cache Issue Type: Bug Security Level: Public (Everyone can see) Affects Versions: 2.0.0.CR1 Reporter: Galder Zamarreno Assigned To: Galder Zamarreno Priority: Minor Fix For: 2.0.0.CR2 I have reproduced an issue via the tutorial but I'm not sure whether it's a tutorial or cache issue yet. Making a note of the steps so that I can come back to it later. 1st GUI: bsh % childFqn2 = Fqn.fromString("/child2"); </child2> bsh % childFqn3 = Fqn.fromString("/child2/child3"); </child2/child3> bsh % child2 = root.addChild(childFqn2); <UnversionedNode[ /child2 data=[]]> bsh % child3 = root.addChild(childFqn3); <UnversionedNode[ /child2/child3 data=[]]> 2nd GUI: bsh % childFqn2 = Fqn.fromString("/child2"); </child2> bsh % child2 = root.getChild(childFqn2); <UnversionedNode[ /child2 data=[] child=[UnversionedNode[ /child2/child3 data=[]]]]> bsh % child2.put("key3", "value3"); <null> - Click on child2 in the 2nd GUI bsh % child2.clearData(); 1st GUI: bsh % child2.put("key3", "value3"); <null> bsh % root.removeChild(childFqn2); <true> child2 node is still in memory which shouldn't. -- 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

1
5
0 / 0

[JBoss JIRA] Created: (JBCACHE-1041) Tutorial - GUI/beanshell block if node modified within transaction and

by Galder Zamarreno (JIRA)

Tutorial - GUI/beanshell block if node modified within transaction and node status queried via GUI MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit Precedence: bulk Tutorial - GUI/beanshell block if node modified within transaction and Tutorial - GUI/beanshell block if node modified within transaction and node status queried via GUI --------------------------------------------------------------------------------------------------------------------------------------------------------------------------- Key: JBCACHE-1041 URL: http://jira.jboss.com/jira/browse/JBCACHE-1041 Project: JBoss Cache Issue Type: Bug Security Level: Public (Everyone can see) Affects Versions: 2.0.0.CR1 Reporter: Galder Zamarreno Assigned To: Galder Zamarreno Priority: Minor Fix For: 2.0.0.CR2 Instructions: - add a node to the cache - start a transaction - do a put on that node - clicking on the node via the GUI to check that the node has not been updated blocks both the GUI and the beanshell. This is due to not being able to acquire the read lock on the node to show it. - Also, once the exception is thrown, the GUI/beanshell stops which shouldn't. Solution: - Updates on the GUI should be handled in a different thread so that it does not block the shell? While the shell is blocked, the current transaction cannot be committed, leaving the user no option. -- 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

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 May 2007