-
Improvement
-
Resolution: Fixed
-
Major
-
2.5
-
None
In earlier versions of tupelo, the stored type was managed and preserved by the system. This cause a lot of needless conversion and was removed in Tupelo 2.5. Unfortunately this also removed a way to control how the values are stored. There is no high-level way to specify this in Tupelo 2.5.
Task: Figure out high-level way to specify stored type (probably a ton more addProperty methods) so that something like this may be done:
addProperty(Resource predicate, String propertyName, Class javaTypeInBean, Class storedType)
E.g. addProperty(Dc.IDENTIFIER, "uri", String.class, URI.class)
The session should resurrect its machinery for doing conversions in those cases where there is a difference between stored and bean types. Tests should be included.