-
1. Re: JBMICROCONT-172 and property editors
If you are going to do property editors then you should use the TypeInfo.convertValue()
instead of creating a whole new place to fix when somebody wants to change the logic
or finds a bug. -
2. Re: JBMICROCONT-172 and property editors
"adrian@jboss.org" wrote:
Why did you add support for PropertyEditors?
It's optional. ;-)"adrian@jboss.org" wrote:
A bean's name or an injection name doesn't support them so isn't this useless?
So why is name and aliases then Object? :-)"adrian@jboss.org" wrote:
And probably confusing if somebody tries it? :-)
"12345".equals(new Integer(12345)) == false
When we get a user that is confused with this, I'll personally make sure he get the right info. ;-) -
3. Re: JBMICROCONT-172 and property editors
"alesj" wrote:
"adrian@jboss.org" wrote:
A bean's name or an injection name doesn't support them so isn't this useless?
So why is name and aliases then Object? :-)
Perhaps this should be in the FAQ? :-)
http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4025033#4025033 -
4. Re: JBMICROCONT-172 and property editors
"adrian@jboss.org" wrote:
If you are going to do property editors then you should use the TypeInfo.convertValue()
instead of creating a whole new place to fix when somebody wants to change the logic
or finds a bug.
Sure, but how to get a TypeInfo instance of the clazz in AbstractAliasMetaData?
Static [Introspection]TypeInfoFactory instance + context classloader in AbstractAliasMetaData?