August 2006 - jboss-dev-forums - Jboss List Archives

[Design of JBoss internal QA (Test Suite)] - Re: Issue of temporary message destinations for HEAD testsui

by ryan.campbell＠jboss.com

Agreed, things need to be consistent across all branches. View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3963315#3963315 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=3963315

19 years, 8 months

1
0
0 / 0

[Design of JBoss internal QA (Test Suite)] - Re: Issue of temporary message destinations for HEAD testsui

by anil.saldhana＠jboss.com

Only a handful of tests depend on the temporary destinations. So choices are: a) Retrofit all the tests (in the 3 branches) to deploy their own local resources (This is the ideal situation). But the effort involved is not worth it at the moment. OR b) Copy the destination-service.xml as part of the "one-test" target and put an echo message at the end, stating that if the test failed, try with all config as the running instance. Remember "one-test" is just a shortcut target (so not high priority). IMHO we should keep the tests(resources including) consistent across branches. There may be others who have different opinion. View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3963313#3963313 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=3963313

19 years, 8 months

1
0
0 / 0

[Design of JBoss internal QA (Test Suite)] - Re: Issue of temporary message destinations for HEAD testsui

by jaroslaw.kijanowski

"But the issue that is uncertain is will be the running jboss instance be the "all" config instance. We cannot make that assumption. " That's the reason why every test should provide its own resources, like severel tests already do. They deploy jar files which describe, which queues and topics are needed during the test. But Anil, you said, that this would cost a lot of time to rewrite the rest of the tests to do so. On the other hand, we can say, that the most tests needs the "all" config (which would bound all needed queues/topics at the startup) and revert these few tests, so they will not deploy the needed resources. I can try to do this. So my question is, what is the strategy for the testsuite? Reverting some tests and say, that most tests require the "all" instance OR changing the conception of the most tests, so that every test has to provide its own resources, that means deploying them on the start of the test and undeploying them on the end. But wouldn't this increase the time of running the testsuite, when every test will deploy its own resources? View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3963303#3963303 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=3963303

19 years, 8 months

1
0
0 / 0

[Design of POJO Server] - Re: JBAS-1841 - ServiceController/Microcontainer integration

by scott.stark＠jboss.org

The eclipse workspace is now building. You need to checkout the https://svn.jboss.org/repos/jbossas/branches/MC_VDF_WORK/system-jmx project and update your entire workspace to pickup all of the updated .classpath files that reference this. The ant scripts are broken and need to be updated after defining the system-jmx artifacts. Note that there is one potential problem in that there are two DeploymentException (org.jboss.deployers.spi, org.jboss.deployment) and there should really only be one (org.jboss.deployers.spi). I guess the correct thing to do is make org.jboss.deployment.DeploymentException a trivial subclass of org.jboss.deployers.spi.DeploymentException, but all uses should be updated as part of the deployer update and the org.jboss.deployment should just go away. View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3963300#3963300 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=3963300

19 years, 8 months

1
0
0 / 0

[Design of JBoss Build System] - Re: docbook support in repository

by rloehr＠jboss.com

The easiest thing to get you going for now is just to check out the doc-book support project alongside your own. svn co https://svn.jboss.org/repos/jbossas/trunk/docbook-support This is how jboss-cache, for example, currently operates. It might make sense to have this become a standalone project and be integrated via binary support in the long-term..... View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3963269#3963269 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=3963269

19 years, 8 months

1
0
0 / 0

[Design of POJO Server] - Re: JBAS-1841 - ServiceController/Microcontainer integration

by scott.stark＠jboss.org

The system/system-jmx split is underway and the branch is broken. Once I have the eclipse workspace building I'll let you know. View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3963263#3963263 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=3963263

19 years, 8 months

1
0
0 / 0

[Javassist development Forum] - "Illegal exception table range" preverify error

by thematrix

Hi, I encountered the following error: Error preverifying class Test VERIFIER ERROR Test.open()V: Illegal exception table range after trying to copy a constructor body to a new method with the following instructions: (final code is the body of the constructor) MethodInfo mf = cf.getMethod(""); mf.setName("open"); CodeAttribute ca = mf.getCodeAttribute(); CodeAttribute codeAttribute = new CodeAttribute(ca.getConstPool(), ca.getMaxStack(), ca.getMaxLocals(), finalCode, ca.getExceptionTable()); It only doesn´t work if in the original constructor includes a try() catch() statement. Does anyone has a solution for the problem? Thanks a lot in advance Regards, theamtrix View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3963260#3963260 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=3963260

19 years, 8 months

1
0
0 / 0

[Design of JBoss jBPM] - Re: Deploying to 3.2 CVS Head

by jonabbey

"tom.baeyens(a)jboss.com" wrote : what about the ant target ? | | if i recall correctly, you have to put the jbpm lib in the ant/lib folder and then put the jbpm configuration resources in the classpath in which you declare the ant tasks. Ugh, why is it necessary to put these libs in the ant/lib folder, rather than declaring an appropriate lib in the build.xml file itself? The build/readme.html file did mention the need to put the jbpm jar files in the ant/lib folder, as well as the existence of a target to automate this, but I don't think we really want to clutter up our centralized ant tree with miscellany like this.. ? View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3963259#3963259 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=3963259

19 years, 8 months

1
0
0 / 0

[Design of POJO Server] - Re: JBAS-1841 - ServiceController/Microcontainer integration

by scott.stark＠jboss.org

"adrian(a)jboss.org" wrote : | I don't know what you mean? | | The tests I have use a mock SARDeployer, | org.jboss.test.system.controller.SimpleSARDeployer | the rest of the code is just a simplified version of the old ServerLoader, | see: org.jboss.test.system.controller.ControllerTestDelegate | Ok, just was not sure if you were trying to test by running the full server. View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3963249#3963249 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=3963249

19 years, 8 months

1
0
0 / 0

[Design of POJO Server] - Re: JBAS-1841 - ServiceController/Microcontainer integration

by adrian＠jboss.org

"scott.stark(a)jboss.org" wrote : Yes. I have already made a few changes. We need to agree on how we test this as currently the server is not booting. Are there local unit tests for this? I don't know what you mean? The tests I have use a mock SARDeployer, org.jboss.test.system.controller.SimpleSARDeployer the rest of the code is just a simplified version of the old ServerLoader, see: org.jboss.test.system.controller.ControllerTestDelegate | public void setUp() throws Exception | { | super.setUp(); | | //System.setProperty(ServerConstants.MBEAN_SERVER_BUILDER_CLASS_PROPERTY, ServerConstants.DEFAULT_MBEAN_SERVER_BUILDER_CLASS); | server = MBeanServerFactory.createMBeanServer("jboss"); | serviceController = createServiceController(); | server.registerMBean(serviceController, ServiceControllerMBean.OBJECT_NAME); | | deployer = new SimpleSARDeployer(server, serviceController); | View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3963241#3963241 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=3963241

19 years, 8 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-dev-forums August 2006