[jboss-dev-forums] [Design of POJO Server] - Re: @JMX aspect and aop/mc integration
scott.stark@jboss.org
do-not-reply at jboss.com
Wed Nov 15 12:41:49 EST 2006
"bstansberry at jboss.com" wrote : Also, is use of an enum allowed in the microcontainer (I don't know enough about the retroweaver to know). And can jbossxb populate an enum from a XML string? There was a mention of that on another thread, but I don't know if it happened. If either of the above are issues, we can just use a string.
|
jbossretro supports enums fine. The mc does not treat enums and strings as interchangable as is the case for other primiatives and their object wrappers. I added a testEnum to the org.jboss.test.kernel.config.test.ConfigureAttributeFromStringTestCase test and its failing:
| java.lang.IllegalArgumentException: Wrong arguments. setEnumProperty for target org.jboss.test.kernel.config.support.SimpleBean at 150bd4d expected=[org.jboss.test.kernel.config.support.SimpleBean$Alphabet] actual=[java.lang.String]
| at org.jboss.reflect.plugins.introspection.ReflectionUtils.handleErrors(ReflectionUtils.java:224)
| at org.jboss.reflect.plugins.introspection.ReflectionUtils.invoke(ReflectionUtils.java:59)
| at org.jboss.reflect.plugins.introspection.ReflectMethodInfoImpl.invoke(ReflectMethodInfoImpl.java:108)
| at org.jboss.joinpoint.plugins.BasicMethodJoinPoint.dispatch(BasicMethodJoinPoint.java:66)
| at org.jboss.test.kernel.config.test.AbstractKernelConfigTest.configure(AbstractKernelConfigTest.java:130)
| at org.jboss.test.kernel.config.test.ConfigureAttributeFromStringTestCase.configureSimpleBean(ConfigureAttributeFromStringTestCase.java:239)
| at org.jboss.test.kernel.config.test.ConfigureAttributeFromStringTestCase.testEnum(ConfigureAttributeFromStringTestCase.java:209)
| at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
| at sun.reflect.NativeMethodAccessorImpl.invoke(Unknown Source)
| at sun.reflect.DelegatingMethodAccessorImpl.invoke(Unknown Source)
| at java.lang.reflect.Method.invoke(Unknown Source)
| at junit.framework.TestCase.runTest(TestCase.java:154)
| at junit.framework.TestCase.runBare(TestCase.java:127)
| at junit.framework.TestResult$1.protect(TestResult.java:106)
| at junit.framework.TestResult.runProtected(TestResult.java:124)
| at junit.framework.TestResult.run(TestResult.java:109)
| at junit.framework.TestCase.run(TestCase.java:118)
| at org.eclipse.jdt.internal.junit.runner.junit3.JUnit3TestReference.run(JUnit3TestReference.java:128)
| at org.eclipse.jdt.internal.junit.runner.TestExecution.run(TestExecution.java:38)
| at org.eclipse.jdt.internal.junit.runner.RemoteTestRunner.runTests(RemoteTestRunner.java:460)
| at org.eclipse.jdt.internal.junit.runner.RemoteTestRunner.runTests(RemoteTestRunner.java:673)
| at org.eclipse.jdt.internal.junit.runner.RemoteTestRunner.run(RemoteTestRunner.java:386)
| at org.eclipse.jdt.internal.junit.runner.RemoteTestRunner.main(RemoteTestRunner.java:196)
|
I'll take a look at it today and if its simple add it for the beta mc release.
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3986242#3986242
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=3986242
More information about the jboss-dev-forums
mailing list