March 2008 - jboss-jira - Jboss List Archives

[JBoss JIRA] Updated: (JBMICROCONT-25) Configurator tidyup

by Ales Justin (JIRA)

[ http://jira.jboss.com/jira/browse/JBMICROCONT-25?page=all ] Ales Justin updated JBMICROCONT-25: ----------------------------------- Fix Version/s: JBossMC.2.0.0.CR1 (was: JBossMC-2.0.0.Beta11) > Configurator tidyup > ------------------- > > Key: JBMICROCONT-25 > URL: http://jira.jboss.com/jira/browse/JBMICROCONT-25 > Project: JBoss MicroContainer > Issue Type: Task > Components: Configurator > Reporter: Adrian Brock > Assigned To: Ales Justin > Priority: Minor > Fix For: JBossMC.2.0.0.CR1 > > > The Configurator api is largely being replaced by the JoinPointFactory api. > There is still a usecase for some of the Configurator api as a convenience mechanism > on top of the JoinPointFactory. > This needs cleaning up. -- 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, 4 months

1
0
0 / 0

[JBoss JIRA] Updated: (JBMICROCONT-25) Configurator tidyup

by Ales Justin (JIRA)

[ http://jira.jboss.com/jira/browse/JBMICROCONT-25?page=all ] Ales Justin updated JBMICROCONT-25: ----------------------------------- JBoss Forum Reference: http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4137495 (was: http://www.jboss.org/index.html?module=bb&op=viewtopic&t=59867) Old forum post: - http://www.jboss.org/index.html?module=bb&op=viewtopic&t=59867 > Configurator tidyup > ------------------- > > Key: JBMICROCONT-25 > URL: http://jira.jboss.com/jira/browse/JBMICROCONT-25 > Project: JBoss MicroContainer > Issue Type: Task > Components: Configurator > Reporter: Adrian Brock > Assigned To: Ales Justin > Priority: Minor > Fix For: JBossMC.2.0.0.CR1 > > > The Configurator api is largely being replaced by the JoinPointFactory api. > There is still a usecase for some of the Configurator api as a convenience mechanism > on top of the JoinPointFactory. > This needs cleaning up. -- 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, 4 months

1
0
0 / 0

[JBoss JIRA] Reopened: (JBMICROCONT-25) Configurator tidyup

by Ales Justin (JIRA)

[ http://jira.jboss.com/jira/browse/JBMICROCONT-25?page=all ] Ales Justin reopened JBMICROCONT-25: ------------------------------------ Check what actually gets used, e.g. use BeanInfo/PropertyInfo for get/set instead. > Configurator tidyup > ------------------- > > Key: JBMICROCONT-25 > URL: http://jira.jboss.com/jira/browse/JBMICROCONT-25 > Project: JBoss MicroContainer > Issue Type: Task > Components: Configurator > Reporter: Adrian Brock > Assigned To: Ales Justin > Priority: Minor > Fix For: JBossMC-2.0.0.Beta11 > > > The Configurator api is largely being replaced by the JoinPointFactory api. > There is still a usecase for some of the Configurator api as a convenience mechanism > on top of the JoinPointFactory. > This needs cleaning up. -- 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, 4 months

1
0
0 / 0

[JBoss JIRA] Resolved: (JBCACHE-474) Compatibility fwk for all classes passed on the wire

by Manik Surtani (JIRA)

[ http://jira.jboss.com/jira/browse/JBCACHE-474?page=all ] Manik Surtani resolved JBCACHE-474. ----------------------------------- Fix Version/s: (was: 2.2.0.GA) Resolution: Out of Date > Compatibility fwk for all classes passed on the wire > ---------------------------------------------------- > > Key: JBCACHE-474 > URL: http://jira.jboss.com/jira/browse/JBCACHE-474 > Project: JBoss Cache > Issue Type: Feature Request > Security Level: Public(Everyone can see) > Affects Versions: 1.2.4SP1 > Reporter: Manik Surtani > Assigned To: Manik Surtani > > Classes that are serialized: > Fqn > MethodCall (JG?) > *Exception > GlobalTransaction > State transfers > 1) Lets use JGroups Streamable where possible (dependency? Externalizable instead?) > 2) Provide a header short containing version > 3) Use a MarshallingFactory for each version so we can understand messages from older installations > 4) Provide MarshallingFactories as plugins so old versions can talk to newer versions (fwd compat) > Object unmarshal(short version, Class type, InputStream is) > { > // if plugin directory empty or unset || version == currentVersion, revert back to existing mechanism > // else > // Look up UnmarshallerPlugin in the compat table (populated at startup with the contents of the plugin dir) > // Lookup based on version and class type. Unmarshaller then extracts and regenerates the relevant object. > } > Unit test as well. > Standalone fwk? jboss-compat.jar + plugins. -- 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, 4 months

1
0
0 / 0

[JBoss JIRA] Created: (JBCACHE-989) Create performance test suite to test failover

by Manik Surtani (JIRA)

Create performance test suite to test failover ---------------------------------------------- Key: JBCACHE-989 URL: http://jira.jboss.com/jira/browse/JBCACHE-989 Project: JBoss Cache Issue Type: Task Security Level: Public (Everyone can see) Reporter: Manik Surtani Assigned To: Manik Surtani Fix For: 2.0.0.GA Should be ideally integrated into cruise control builds, and should test a variety of configurations including sync and async replication, BR, etc. -- 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, 4 months

1
5
0 / 0

[JBoss JIRA] Updated: (JBCACHE-89) Allow Specifying Custom Interceptors in XML Configuration

by Manik Surtani (JIRA)

[ http://jira.jboss.com/jira/browse/JBCACHE-89?page=all ] Manik Surtani updated JBCACHE-89: --------------------------------- Fix Version/s: 3.0.0 (was: 2.2.0.GA) > Allow Specifying Custom Interceptors in XML Configuration > --------------------------------------------------------- > > Key: JBCACHE-89 > URL: http://jira.jboss.com/jira/browse/JBCACHE-89 > Project: JBoss Cache > Issue Type: Feature Request > Affects Versions: 1.2 > Reporter: Daniel Gredler > Assigned To: Manik Surtani > Fix For: 3.0.0 > > Original Estimate: 1 day > Time Spent: 30 minutes > Remaining Estimate: 7 hours, 30 minutes > > It would be nice to be able to add interceptors via the XML configuration files. Indeed, in TreeCache.java the following comment exists, which may indicate that this feature is already planned: > // Create the interceptors in the correct order (later to be defined in XML file) > createInterceptorChain(); > A possible example configuration would be: > <server> > <classpath codebase="./lib" archives="jboss-cache.jar, jgroups.jar" /> > <mbean code="org.jboss.cache.TreeCache" name="jboss.cache:service=TreeCache"> > ... > <attribute name="Interceptors"> > <interceptor>com.foo.project.MyInterceptor</interceptor> > </attribute> > ... > </mbean> > </server> > Something along the lines of the following method would then be able to add the custom interceptors (in TreeCache.java): > public void setInterceptors(Element interceptors) throws Exception { > NodeList list = interceptors.getChildNodes(); > for(int i = 0; i < list.getLength(); i++) { > org.w3c.dom.Node node = list.item(i); > if(node.getNodeType() != org.w3c.dom.Node.ELEMENT_NODE) > continue; > NodeList children = node.getChildNodes(); > if(children.getLength() != 1) > continue; > org.w3c.dom.Node childNode = list.item(0); > if(childNode.getNodeType() != org.w3c.dom.Node.TEXT_NODE) > continue; > String className = childNode.getNodeValue(); > if(className == null || className.length() == 0) > continue; > Interceptor interceptor = createInterceptor(className); > addInterceptor(interceptor_chain, interceptor); > } > } -- 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, 4 months

1
0
0 / 0

[JBoss JIRA] Resolved: (JBCACHE-315) Break locks for state transfer

by Manik Surtani (JIRA)

[ http://jira.jboss.com/jira/browse/JBCACHE-315?page=all ] Manik Surtani resolved JBCACHE-315. ----------------------------------- Fix Version/s: (was: 2.2.0.GA) Resolution: Won't Fix Makes more sense to focus on the new state transfer mechanism in JBCACHE-1236 > Break locks for state transfer > ------------------------------ > > Key: JBCACHE-315 > URL: http://jira.jboss.com/jira/browse/JBCACHE-315 > Project: JBoss Cache > Issue Type: Feature Request > Security Level: Public(Everyone can see) > Reporter: Bela Ban > Assigned To: Vladimir Blagojevic > Priority: Critical > > State transfer needs to acquire a lock on the root to make sure all existing TXs have been completed. However, when a TX takes more time than the lock acquisition timeout, state transfer will fail. > Therefore, we need to forcefully acquire the locks for the state transfer by force-releasing the existing locks, and rolling back all TXs that held those locks. > This will ensure that state transfer always succeeds, at the expense of some rolled back TXs. > We need to investigate how this works with optimistic locking -- 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, 4 months

1
0
0 / 0

[JBoss JIRA] Closed: (JBMICROCONT-25) Configurator tidyup

by Adrian Brock (JIRA)

[ http://jira.jboss.com/jira/browse/JBMICROCONT-25?page=all ] Adrian Brock closed JBMICROCONT-25. ----------------------------------- Fix Version/s: JBossMC-2.0.0.Beta11 (was: JBossMC.2.0.0.CR1) Resolution: Done > Configurator tidyup > ------------------- > > Key: JBMICROCONT-25 > URL: http://jira.jboss.com/jira/browse/JBMICROCONT-25 > Project: JBoss MicroContainer > Issue Type: Task > Components: Configurator > Reporter: Adrian Brock > Assigned To: Ales Justin > Priority: Minor > Fix For: JBossMC-2.0.0.Beta11 > > > The Configurator api is largely being replaced by the JoinPointFactory api. > There is still a usecase for some of the Configurator api as a convenience mechanism > on top of the JoinPointFactory. > This needs cleaning up. -- 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, 4 months

1
0
0 / 0

[JBoss JIRA] Reopened: (JBMICROCONT-25) Configurator tidyup

by Adrian Brock (JIRA)

[ http://jira.jboss.com/jira/browse/JBMICROCONT-25?page=all ] Adrian Brock reopened JBMICROCONT-25: ------------------------------------- > Configurator tidyup > ------------------- > > Key: JBMICROCONT-25 > URL: http://jira.jboss.com/jira/browse/JBMICROCONT-25 > Project: JBoss MicroContainer > Issue Type: Task > Components: Configurator > Reporter: Adrian Brock > Assigned To: Ales Justin > Priority: Minor > Fix For: JBossMC-2.0.0.Beta11 > > > The Configurator api is largely being replaced by the JoinPointFactory api. > There is still a usecase for some of the Configurator api as a convenience mechanism > on top of the JoinPointFactory. > This needs cleaning up. -- 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, 4 months

1
0
0 / 0

[JBoss JIRA] Updated: (JBCACHE-295) Add unit tests for ReplicationQueue

by Manik Surtani (JIRA)

[ http://jira.jboss.com/jira/browse/JBCACHE-295?page=all ] Manik Surtani updated JBCACHE-295: ---------------------------------- Component/s: Scripts and processes > Add unit tests for ReplicationQueue > ----------------------------------- > > Key: JBCACHE-295 > URL: http://jira.jboss.com/jira/browse/JBCACHE-295 > Project: JBoss Cache > Issue Type: Task > Security Level: Public(Everyone can see) > Components: Scripts and processes > Reporter: Brian Stansberry > Assigned To: Brian Stansberry > Priority: Minor > Fix For: 2.2.0.GA > > -- 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, 4 months

1
0
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 March 2008