[jboss-dev-forums] [Design the new POJO MicroContainer] - Re: UnwrapValueUnitTestCase.testCollectionUnwrap failure on
alesj
do-not-reply at jboss.com
Thu Nov 20 07:08:34 EST 2008
"scott.stark at jboss.org" wrote : The problem is in determining the component type when a java.util.Set generic is passed in. In this case its a Set[TestEnum], but the component type is determined to be java.lang.Integer.
|
| | 441 DEBUG [DefaultMetaValueFactory] unwrapCollection, type: ReflectClassInfoImpl at 30cb4b{name=java.util.Set}
| | 441 DEBUG [DefaultMetaValueFactory] unwrapCollection, componentType: java.lang.Integer
| | 443 DEBUG [DefaultMetaValueFactory] convertValue failure(For input string: "TWO"), value=TWO, value.class: java.lang.String, typeInfo: java.lang.Integer
| |
|
| Just adding a logging statement can change the failure or even fix the problem. Its some issue with reflection on the generic element type that is suspect.
|
This looks like caching issue.
See UnwrapValueUnitTestCase::testCollectionUnwrap.
Before Enums we test Integers.
Looks like Set.class is mapped to ClassInfo who's component type is
a leftover from previous Integers testing.
I'll dig into more.
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4190846#4190846
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4190846
More information about the jboss-dev-forums
mailing list