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

[Design of JBoss jBPM] - Re: Missing jars from JBoss AS 4.0.4GA Patch1 EJB Profile

by jeffdelong

Well I would not want to see having to maintain two versions that would require two different downloads, etc. View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3986307#3986307 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=3986307

19 years, 4 months

1
0
0 / 0

[Design the new POJO MicroContainer] - Re: AOPConstructorJoinpoint after JBAOP-307

by alesj

Eh, just forget about this. Thought build-thirdparty is called from some main build.xml. Simple running of it did the trick. :-( View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3986295#3986295 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=3986295

19 years, 4 months

1
0
0 / 0

[Design the new POJO MicroContainer] - AOPConstructorJoinpoint after JBAOP-307

by alesj

It won't compile with [my] current aop lib. Cannot find AOPProxyFactoryParameters.setCtor method. How to get the last aop from repository - which ant task? View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3986293#3986293 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=3986293

19 years, 4 months

1
0
0 / 0

[Design of JBoss internal QA (Test Suite)] - Re: Logging with JBossTestCase

by scott.stark＠jboss.org

ctors cannot be calling non-private methods as you cannot guarantee that they will behave correctly. All of the initialization and logging in test class ctors is fragile and subject to being broken like has happened with this refactoring, and needs to be revised. View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3986291#3986291 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=3986291

19 years, 4 months

1
0
0 / 0

[Design of JBoss internal QA (Test Suite)] - Re: Logging with JBossTestCase

by rachmatowicz＠jboss.com

An example of the problem is if you want to write to the log from a test case constructor for some reason. The class below subclasses from JBossTestCase: public MessageBodyUnitTestCase(String name) throws Exception { super(name); // this should return null log = getLog(); if (log == null) System.out.println("MessageBodyUnitTestCase: null returned") ; } protected void setUp() throws Exception { // call setUp() in the superclass super.setUp() ; connect(); } protected void tearDown() throws Exception { disconnect(); // call tearDown() in the superclass to cleanup super.tearDown() ; } The test execution shows that the log is not correctly initialsed by the time the construtor gets executed: java.lang.NullPointerException at org.jboss.test.jbossmessaging.test.MessageBodyUnitTestCase.connect(MessageBodyUnitTestCase.java:95) at org.jboss.test.jbossmessaging.test.MessageBodyUnitTestCase.setUp(MessageBodyUnitTestCase.java:82) at junit.extensions.TestDecorator.basicRun(TestDecorator.java:22) at junit.extensions.TestSetup$1.protect(TestSetup.java:19) at junit.extensions.TestSetup.run(TestSetup.java:23) <system-out><![CDATA[MessageBodyUnitTestCase: null returned MessageBodyUnitTestCase: null returned This state of affairs also holds for JBossTestCase's constructor as well - so the exception handling code won't work in initDelegate. But i'll change the logging arrange,ent to call getLog() when a log reference is needed, and put any once-per-test-suite stuff in a JBossTestSetup wrapper. View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3986290#3986290 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=3986290

19 years, 4 months

1
0
0 / 0

[Design of JBoss Labs] - Re: Default Blog Portlet Behavior

by mmontoni

Hi, I just ran thru this thread and I wonder if the Blog Portlet is read and available for use.... Thanks Mariella. View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3986288#3986288 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=3986288

19 years, 4 months

1
0
0 / 0

[Design of JBoss jBPM] - Re: Missing jars from JBoss AS 4.0.4GA Patch1 EJB Profile

by david.lloyd＠jboss.com

Yes and no... We could produce a JDK 5 version that skips the "retro" phase, and a separate 1.4 version that does the jbossretro bit and requires the two jars. This is what the JBossWS guys do, and other projects are doing it as well I believe. JBossAS ships with the 1.4 version. Of course for them it's a matter of spec compliance - they have to be able to run on the 1.4 JDK to be compliant with j2ee 1.4. I'm open to this possibility if Tom agrees. View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3986285#3986285 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=3986285

19 years, 4 months

1
0
0 / 0

[Design of JBoss internal QA (Test Suite)] - Re: Logging with JBossTestCase

by scott.stark＠jboss.org

"rachmatowicz(a)jboss.com" wrote : | But I believe there are still problems here: | 1. JBossTestCase uses logging provided by BaseTestCase, but it does not call setUp() or tearDown(). Also, test class constructors seem to get called by JUnit before setUp() methods. Thus, I believe that any use of logging in JBossTestCase (for example, when handling exceptions in initDelegate()) will not be properly initialised by that time, as setUp() will not yet have been called. | Doing initialization from the ctor is bad. This should be moved to a setUp/tearDown. "rachmatowicz(a)jboss.com" wrote : | 2. The setUp() and tearDown() methods are called each time a testcase is run. So it appears that logging will be set up and torn down for every test case, as opposed to once every test suite. It may be more appropriate to arrange things so that either this setup was done in a one time setup/teardown wrapper, as in AbstractTestCaseWithSetup, or arrange for logging setup outside of the methods setUp() and tearDown(). But AbstractTestCaseWithSetup would probably need some alteration as it is currently tuned to run with Joram tests. See related: http://www.jboss.com/index.html?module=bb&op=viewtopic&t=91386&postdays=0... | This is a function of how you run the test. If we are running multiple tests there should be a TestSuite wrapper. If your running a single tests from within an ide you want a per test setUp/tearDown. "rachmatowicz(a)jboss.com" wrote : | 3. If setUp() and tearDown() are used as the means for initialising logging, would it help programmers if those methods were overridden in JBossTestCase to call super.setUp() and super.tearDown(), to make it more obvious that there was important work being done in superclasses with these methods? | The JBossTest* classes in the jbossas suite need to be brought in synch with the base test project classes. If there are changes needed to do that in the test project, that is fine as long as they are discussed. View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3986283#3986283 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=3986283

19 years, 4 months

1
0
0 / 0

[Design of JBoss internal QA (Test Suite)] - Logging with JBossTestCase

by rachmatowicz＠jboss.com

There have been some changes to the class hierarchy involving JBossTestCase. It used to subclass from junit.framework.TestCase. It now subclasses from org.jboss.test.BaseTestCase which in turn subclasses from org.jboss.test.AbstractTestCase. BaseTestCase provides a getLog() method, something which JBossTestCase used to do. But in order for logging to be set up correctly, a subclass X of JBossTestCase must ensure that setUp() is called in BaseTestCase. If X does not override setUp() or tearDown(), it need take no action, as the method will be inherited; if it does override setUp() or tearDown(), it needs to call super.setUp() and super.tearDown() in the overriding methods. But I believe there are still problems here: 1. JBossTestCase uses logging provided by BaseTestCase, but it does not call setUp() or tearDown(). Also, test class constructors seem to get called by JUnit before setUp() methods. Thus, I believe that any use of logging in JBossTestCase (for example, when handling exceptions in initDelegate()) will not be properly initialised by that time, as setUp() will not yet have been called. 2. The setUp() and tearDown() methods are called each time a testcase is run. So it appears that logging will be set up and torn down for every test case, as opposed to once every test suite. It may be more appropriate to arrange things so that either this setup was done in a one time setup/teardown wrapper, as in AbstractTestCaseWithSetup, or arrange for logging setup outside of the methods setUp() and tearDown(). But AbstractTestCaseWithSetup would probably need some alteration as it is currently tuned to run with Joram tests. See related: http://www.jboss.com/index.html?module=bb&op=viewtopic&t=91386&postdays=0... 3. If setUp() and tearDown() are used as the means for initialising logging, would it help programmers if those methods were overridden in JBossTestCase to call super.setUp() and super.tearDown(), to make it more obvious that there was important work being done in superclasses with these methods? View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3986279#3986279 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=3986279

19 years, 4 months

1
0
0 / 0

[Design of JBoss jBPM] - Re: Missing jars from JBoss AS 4.0.4GA Patch1 EJB Profile

by jeffdelong

EJB 3 profile probably removes them because EJB3 assumes Java 5. So if the console app is run with Java 5, are the retro jars still required? View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3986273#3986273 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=3986273

19 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-dev-forums November 2006