Bug 175859 [DataBinding] Use MessageFormat for validation hints
The default hints produced by String2IntegerPrimitiveValidator and its peers are not very pleasant. They print extremely long numbers, are missing spaces, etc. For I18n, these hints should be produced via MessageFormat patterns, rather than with a hard-coded structure. This would also allow clients to override the messages by providing replacement patterns in a fragment. Boris, are there any issues with using java.text.MessageFormat under Foundation profiles? Should an ICU equivalent be used instead?
bundles/org.eclipse.core.databinding/src/org/eclipse/core/databinding/UpdateStrategy.java
private static final String BOOLEAN_TYPE = "java.lang.Boolean.TYPE"; 
	private static final String SHORT_TYPE = "java.lang.Short.TYPE"; 
	private static final String BYTE_TYPE = "java.lang.Byte.TYPE"; 
	private static final String DOUBLE_TYPE = "java.lang.Double.TYPE"; 
	private static final String FLOAT_TYPE = "java.lang.Float.TYPE"; 
	private static final String INTEGER_TYPE = "java.lang.Integer.TYPE"; 
	private static final String LONG_TYPE = "java.lang.Long.TYPE"; 
	private static Map converterMap;
	private static Class autoboxed(Class clazz) {
		if (clazz == Float.TYPE)
			return Float.class;
		else if (clazz == Double.TYPE)
			return Double.class;
		else if (clazz == Short.TYPE)
			return Short.class;
		else if (clazz == Integer.TYPE)
			return Integer.class;
		else if (clazz == Long.TYPE)
			return Long.class;
		else if (clazz == Byte.TYPE)
			return Byte.class;
		else if (clazz == Boolean.TYPE)
			return Boolean.class;
		return clazz;
	}
	final protected void checkAssignable(Object toType, Object fromType,