[Design the new POJO MicroContainer] - Re: Context installation causes StackOverflowError
by alesj
This is the cause.
Just need to see why this is really failing ...
| [INFO] Surefire report directory: C:\projects\microcontainer\kernel\jmx-mc-int\target\surefire-reports
| log4j:WARN No appenders could be found for logger (org.jboss.util.NestedThrowable).
| log4j:WARN Please initialize the log4j system properly.
| org.apache.maven.surefire.booter.SurefireExecutionException: org.jboss.test.system.controller.configure.value.text.test.TextValueTest; nested exception is java.lang.NoClassDefFoundError: org.jboss.test.system.controller.configure.value.text.test.Text
| ValueTest
| java.lang.NoClassDefFoundError: org.jboss.test.system.controller.configure.value.text.test.TextValueTest
| at java.lang.Class.getDeclaredMethods0(Native Method)
| at java.lang.Class.privateGetDeclaredMethods(Class.java:2395)
| at java.lang.Class.getMethod0(Class.java:2642)
| at java.lang.Class.getMethod(Class.java:1579)
| at org.junit.internal.requests.ClassRequest.hasSuiteMethod(ClassRequest.java:61)
| at org.junit.internal.requests.ClassRequest.getRunnerClass(ClassRequest.java:50)
| at org.junit.internal.requests.ClassRequest.getRunner(ClassRequest.java:28)
| at org.apache.maven.surefire.junit4.JUnit4TestSet.<init>(JUnit4TestSet.java:45)
| at org.apache.maven.surefire.junit4.JUnit4DirectoryTestSuite.createTestSet(JUnit4DirectoryTestSuite.java:56)
| at org.apache.maven.surefire.suite.AbstractDirectoryTestSuite.locateTestSets(AbstractDirectoryTestSuite.java:96)
| at org.apache.maven.surefire.Surefire.createSuiteFromDefinition(Surefire.java:209)
| at org.apache.maven.surefire.Surefire.run(Surefire.java:156)
| at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
| at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
| at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
| at java.lang.reflect.Method.invoke(Method.java:585)
| at org.apache.maven.surefire.booter.SurefireBooter.runSuitesInProcess(SurefireBooter.java:345)
| at org.apache.maven.surefire.booter.SurefireBooter.main(SurefireBooter.java:1009)
| [INFO] ------------------------------------------------------------------------
| [ERROR] BUILD FAILURE
View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=4221018#4221018
Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=4221018
17 years
[Design of Management Features on JBoss] - Re: JBAS-6672, null values and defaults
by charles.crouch@jboss.com
Summarizing the discussion from todays console call:
1) When creating a new component, if a managed property is not specified or specified as null, then the profile service should make sure any default value for that property is applied during deployment, but that the default value is *not* persisted as part of the managed view of the component.
2) When viewing a resource created in step 1), any properties which were null originally, should be returned as null by the profile service, i.e. they should not be returned as either the default value for the property or the default value for underlying primitive type, e.g. 0 for int, false for boolean.
3) If the default value for a property changes, and that managed property has a null value (e.g. the user has never specified a value), then when the component gets deployed it should use the new default value.
Cheers
View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=4221000#4221000
Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=4221000
17 years