February 2009 - jboss-dev-forums - Jboss List Archives

[Design of Messaging on JBoss (Messaging/JBoss)] - Re: refactor tests using INVM acceptors/connectors

by jmesnil

"clebert.suconic(a)jboss.com" wrote : | don' t we have tests that share a server start? | I'm not aware of any such test. Do you have an example? "clebert.suconic(a)jboss.com" wrote : | Also: we have lots of tests where tearDown is not calling its super method. Yes, I'm fixing it when I see setUp/tearDown w/o the call to the super methods. The idea is to prevent all the cascading failures asap. I've got a regression in the failover tests and it is impossible to check what's going on with all the noisy cascading failures View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=4212651#4212651 Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=4212651

17 years, 1 month

1
0
0 / 0

[Design of Messaging on JBoss (Messaging/JBoss)] - Re: refactor tests using INVM acceptors/connectors

by clebert.suconic＠jboss.com

"jmesnil" wrote : I'll also add clearing the InVMRegistry in the setUp() of UnitTestCase don' t we have tests that share a server start? Also: we have lots of tests where tearDown is not calling its super method. View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=4212641#4212641 Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=4212641

17 years, 1 month

1
0
0 / 0

[Design of JBoss Build System] - Re: Circular dependencies in release

by pgier

I don't think there is an easy solution. You could just do part of the release manually, you should just have to update the info in and , and then use the release plugin for the rest. If it's really a circular dependency, then maybe in the future you can factor out the parts that are causing the cycle. Maybe api should be separate? View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=4212637#4212637 Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=4212637

17 years, 1 month

1
0
0 / 0

[Design of Messaging on JBoss (Messaging/JBoss)] - Re: refactor tests using INVM acceptors/connectors

by jmesnil

I'll also add clearing the InVMRegistry in the setUp() of UnitTestCase View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=4212613#4212613 Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=4212613

17 years, 1 month

1
0
0 / 0

[Design of Messaging on JBoss (Messaging/JBoss)] - refactor tests using INVM acceptors/connectors

by jmesnil

We have a lot of tests which uses the INVM acceptors. All these tests shares the same INVMRegistry singleton. If a test fails and does not clean up its acceptor(s), all the subsequent tests which try to register an INVM acceptor with the same ID will fail. 1 failing test will result in hundred of failing tests making it very difficult to see regression, esp. since we have a few intermittent failing tests using INVM acceptors. I propose that we refactor every tests using INVM acceptor so that: * in the setUp, we clean up the INVM registry (we don't care what happened before) * in the tearDown, we check that the INVM registry size is set to 0 I'll add a InVMTestCase and use it to extend every tests using INVM acceptor. wdyt? View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=4212612#4212612 Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=4212612

17 years, 1 month

1
0
0 / 0

[Design of JBoss Collaboration Server] - Re: Is this project still active?

by acoliver＠jboss.org

It moved to http://buni.org. It will re-activate there next year. View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=4212565#4212565 Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=4212565

17 years, 1 month

1
0
0 / 0

[Design of JCA on JBoss] - Re: [JBAS-5221] tx-connection-factory/no-tx-connection-facto

by emuckenhuber

I was wondering about this property too, as this seems a bit confusing. Because which of the following is the correct property to edit: | managedObject.getProperty("driver-class"); | // or: | managedObject.getProperty("config-property").get("DriverClass"); | >From a attachment persistence standpoint we could also get some issues with this: e.g. if setManagedConnectionFactoryProperties is writing the changes back to the attachment. And you just update "driver-class", without refreshing the MO (and therefore "config-property") - it could persist two different values for "driver-class" (should be the same problem if you do it the other way around). View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=4212558#4212558 Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=4212558

17 years, 1 month

1
0
0 / 0

[Design of JBoss Collaboration Server] - Is this project still active?

by ryanrlamothe

is this project still active? If not, how can it get re-activated? Thanks! View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=4212489#4212489 Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=4212489

17 years, 1 month

1
0
0 / 0

[Design of JBoss Build System] - Circular dependencies in release

by pete.muir＠jboss.org

I have an SVN structure like this: ri/trunk/api | ri/trunk/impl | ri/trunk/dist | ri/trunk/spi | | examples/trunk/... | | tck/trunk/api | tck/trunk/impl and also off in jbossas/projects webbeans-ri-int/trunk/jbossas | webbeans-ri-int/trunk/mc | webbeans-ri-int/trunk/deployer | webbeans-ri-int/trunk/ejb | | | | To release, I need to things in this order: | | | | * install a release of ri/trunk/api and ri/trunk/spi locally | | * update to RI API and SPI version and install | | * update to the above API version and install | | * install a release of the RI locally | | * update to RI API and tag examples | | * tag tck | | * tag ri-int | | * do some more tags for modules without deps | | * build dist and tag | | | | Now, if I did the release manually, this would be possible, but because the release plugin tags as I go, I don't see how to do this. Ideally, I want to use the release plugin to install locally only in the first 4 steps, and then go back and tag later. | | | | Any suggestions? View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=4212456#4212456 Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=4212456

17 years, 1 month

1
0
0 / 0

[Design of JBoss Identity] - Re: Provisioning

by anil.saldhana＠jboss.com

"david.lloyd(a)jboss.com" wrote : It looks like even SPML would want to use an underlying provisioning API. If the API is properly designed, then SPML or any of the other four things you list should be pretty easy to come up with. Agreed, currently Bolek has been driving the Identity Model in the IDM subproject. IMO provisioning has both push as well pull aspects, the API/SPI that has been generated here: http://anonsvn.jboss.org/repos/jbossidentity/idm/trunk/ The events api is also important for emitting events that may have a bearing on provisioning. http://anonsvn.jboss.org/repos/jbossidentity/idm/trunk/idm-api/src/main/j... View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=4212445#4212445 Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=4212445

17 years, 1 month

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-dev-forums February 2009