It can't be on the TypeInfo because a there is a many to one relationship between ManagedPropertys to a given TyypeInfo, and each MaagedProperty can be overriding how the MetaValue is being built. The ICF should be looking to the MetaMapper attached to the ManagedProperty. There are a few issues with the ICF api that are showing up as we have evolved other features. The MetaMapper should probably be part of the ICF.setValue/getValue calls. For now, we need to review the ICF implementations (there are probably only two) and make sure they are using the full set of type transformation features. View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=4229509#... Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&a...