December 2007 - jboss-jira - Jboss List Archives

[JBoss JIRA] Updated: (JBCACHE-311) Refactor jbosscache to provide an interface for transport

by Manik Surtani (JIRA)

[ http://jira.jboss.com/jira/browse/JBCACHE-311?page=all ] Manik Surtani updated JBCACHE-311: ---------------------------------- Fix Version/s: 3.0.0 (was: 2.2.0.GA) Affects: [Documentation (Ref Guide, User Guide, etc.), Compatibility/Configuration] (was: [Compatibility/Configuration, Documentation (Ref Guide, User Guide, etc.)]) Priority: Major (was: Minor) > Refactor jbosscache to provide an interface for transport > --------------------------------------------------------- > > Key: JBCACHE-311 > URL: http://jira.jboss.com/jira/browse/JBCACHE-311 > Project: JBoss Cache > Issue Type: Feature Request > Security Level: Public(Everyone can see) > Reporter: Nick Betteridge > Assigned To: Manik Surtani > Fix For: 3.0.0 > > > There are many different transports available (jgroups, jboss remoting etc) which are available and which already exist within commnissioned systems. Further, clients requirements/project specification sometimes stipulates a specific transport to be used. JBossCache currently has JGroups embedded as the transport used. If BossCache was refactored to provide a generic transport interface, it would make JBossCache more 'user friendly' so that the features of JBossCache can be used within a greater variety of projects. -- 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, 6 months

1
0
0 / 0

[JBoss JIRA] Commented: (JBCACHE-311) Refactor jbosscache to provide an interface for transport

by Manik Surtani (JIRA)

[ http://jira.jboss.com/jira/browse/JBCACHE-311?page=comments#action_12392319 ] Manik Surtani commented on JBCACHE-311: --------------------------------------- Approach: 1) Remove API dependencies on JGroups classes (see dependent JIRA) 2) RPCManager interface may need further fleshing out, RPCManagerImpl to be renamed to JGroupsRPCManager 3) Move callRemoteMethods and channel ownership to the RPCManager 4) Move all callbacks and remote RPC calls to the RPCManager which will then delegate to the actual cache. > Refactor jbosscache to provide an interface for transport > --------------------------------------------------------- > > Key: JBCACHE-311 > URL: http://jira.jboss.com/jira/browse/JBCACHE-311 > Project: JBoss Cache > Issue Type: Feature Request > Security Level: Public(Everyone can see) > Reporter: Nick Betteridge > Assigned To: Manik Surtani > Priority: Minor > Fix For: 2.2.0.GA > > > There are many different transports available (jgroups, jboss remoting etc) which are available and which already exist within commnissioned systems. Further, clients requirements/project specification sometimes stipulates a specific transport to be used. JBossCache currently has JGroups embedded as the transport used. If BossCache was refactored to provide a generic transport interface, it would make JBossCache more 'user friendly' so that the features of JBossCache can be used within a greater variety of projects. -- 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, 6 months

1
0
0 / 0

[JBoss JIRA] Commented: (JBBUILD-294) Create hudson instance for maven build in app server head.

by Paul Gier (JIRA)

[ http://jira.jboss.com/jira/browse/JBBUILD-294?page=comments#action_12392295 ] Paul Gier commented on JBBUILD-294: ----------------------------------- App server maven builds and related subprojects can be seen in hudson here: http://hudson.qa.jboss.com/hudson/view/JBoss%20AS%20Maven/ > Create hudson instance for maven build in app server head. > ---------------------------------------------------------- > > Key: JBBUILD-294 > URL: http://jira.jboss.com/jira/browse/JBBUILD-294 > Project: JBoss Build System > Issue Type: Task > Components: Maven > Affects Versions: Maven Build 1.1 > Reporter: Ruel Loehr > Assigned To: Paul Gier > Fix For: Maven Build - App Server > > Original Estimate: 2 days > Remaining Estimate: 2 days > > Setup a hudson instance for Maven. -- 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, 6 months

1
0
0 / 0

[JBoss JIRA] Created: (JBAS-4678) Need to write the ManagedOperation aspects for the ProfileService.ManagementView

by Scott M Stark (JIRA)

Need to write the ManagedOperation aspects for the ProfileService.ManagementView -------------------------------------------------------------------------------- Key: JBAS-4678 URL: http://jira.jboss.com/jira/browse/JBAS-4678 Project: JBoss Application Server Issue Type: Task Security Level: Public (Everyone can see) Components: AOP, Management services Reporter: Scott M Stark Assigned To: Ales Justin Fix For: JBossAS-5.0.0.Beta3 An aspect that intercepts the proxied ManagedOperation calls and dispatches the op to the associated runtime component needs to be written. -- 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, 6 months

2
1
0 / 0

[JBoss JIRA] Created: (JBAS-4713) Upgrade to JBoss Cache 2.1.0

by Brian Stansberry (JIRA)

Upgrade to JBoss Cache 2.1.0 ---------------------------- Key: JBAS-4713 URL: http://jira.jboss.com/jira/browse/JBAS-4713 Project: JBoss Application Server Issue Type: Sub-task Security Level: Public (Everyone can see) Components: Clustering Reporter: Brian Stansberry Assigned To: Brian Stansberry Fix For: JBossAS-5.0.0.CR1 Need bug fixes from 2.0.0.GA. Next JBC release on roadmap is 2.1.0, so we'll need that. -- 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, 6 months

1
3
0 / 0

[JBoss JIRA] Created: (JBAS-4712) Upgrade JGroups to 2.6

by Brian Stansberry (JIRA)

Upgrade JGroups to 2.6 ---------------------- Key: JBAS-4712 URL: http://jira.jboss.com/jira/browse/JBAS-4712 Project: JBoss Application Server Issue Type: Sub-task Security Level: Public (Everyone can see) Reporter: Brian Stansberry Assigned To: Brian Stansberry -- 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, 6 months

1
3
0 / 0

[JBoss JIRA] Created: (JBCACHE-1240) Option to create another copy of backup data if data owner dies

by Brian Stansberry (JIRA)

Option to create another copy of backup data if data owner dies --------------------------------------------------------------- Key: JBCACHE-1240 URL: http://jira.jboss.com/jira/browse/JBCACHE-1240 Project: JBoss Cache Issue Type: Feature Request Security Level: Public (Everyone can see) Components: Buddy Replication Reporter: Brian Stansberry Assigned To: Manik Surtani With BR, if a data owner dies, the number of copies of the data it owns is reduced by one. If the data is accessed, another node becomes owner and the number of backups returns to normal. But if the data isn't accessed, the number of backups remains reduced. Besides the general problem of lesser reliability for this data, this can be a problem with things like rolling upgrades, where all the backup nodes could be restarted before the data is accessed, leading to data loss. Downside to making another copy of the backup data when the owner dies is it adds stress to the system by replicating more data. So, this should be configurable. -- 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, 6 months

1
0
0 / 0

[JBoss JIRA] Updated: (JBAS-2149) ByValueContainerInvoker

by Dimitris Andreadis (JIRA)

[ http://jira.jboss.com/jira/browse/JBAS-2149?page=all ] Dimitris Andreadis updated JBAS-2149: ------------------------------------- Fix Version/s: JBossAS-5.0.0.CR1 (was: JBossAS-5.0.0.Beta3) Moving to CR1. If there is a problem with this, please contact me. > ByValueContainerInvoker > ----------------------- > > Key: JBAS-2149 > URL: http://jira.jboss.com/jira/browse/JBAS-2149 > Project: JBoss Application Server > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: Test Suite > Reporter: Adrian Brock > Fix For: JBossAS-5.0.0.CR1 > > > Remove the use of ByValueInvokerInterceptor from the testsuite. > This was deprecated in JBoss4 and removed in JBoss5, it should be using the MarshalledInvokerInterceptor. -- 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, 6 months

1
0
0 / 0

[JBoss JIRA] Created: (JBAS-4398) implement instances of JBMICROCONT-178

by Mark Spritzler (JIRA)

implement instances of JBMICROCONT-178 -------------------------------------- Key: JBAS-4398 URL: http://jira.jboss.com/jira/browse/JBAS-4398 Project: JBoss Application Server Issue Type: Sub-task Security Level: Public (Everyone can see) Components: ProfileService Reporter: Mark Spritzler implement the new interfaces defined by JBMICROCONT-178 -- 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, 6 months

2
2
0 / 0

[JBoss JIRA] Created: (JBPORTAL-1843) NPE when trying to access remote portlets

by Chris Laprun (JIRA)

NPE when trying to access remote portlets ----------------------------------------- Key: JBPORTAL-1843 URL: http://jira.jboss.com/jira/browse/JBPORTAL-1843 Project: JBoss Portal Issue Type: Bug Security Level: Public (Everyone can see) Components: Portal Core Admin Affects Versions: 2.6.3 Final Reporter: Chris Laprun Assigned To: Chris Laprun Fix For: 2.6.4 Final java.lang.NullPointerException at org.jboss.portal.core.admin.ui.AdminPropertyResolver.getValueForRequestLocale(AdminPropertyResolver.java:444) at org.jboss.portal.core.admin.ui.AdminPropertyResolver.access$000(AdminPropertyResolver.java:76) at org.jboss.portal.core.admin.ui.AdminPropertyResolver$3.getValue(AdminPropertyResolver.java:131) -- 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, 6 months

1
1
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

jboss-jira December 2007