14 Jan
2010
14 Jan
'10
7:10 p.m.
On Jan 14, 2010, at 9:40 AM, Vincent Massol wrote:
Hi some notes (for myself to remember and for
visibility) about what's left to do with Entity References before 2.2 final:
1) Continue migrating code to use reference objects instead of Strings. XWikiDocument
class mostly done (but some work remain). Next to do: hibernate store, XWiki class. Then
API package classes.
2) Decide how we handle velocity scripts. Either we handle reference objects in velocity
or we continue to use strings. Note that some vm files currently do stuff like: $somespace
+ "." + $doc.name
3) Decide if we want to check for null names in EntityReference. If we do then we cannot
use the normalizing feature for nulls anymore, which is useful. In this case we'd need
to find another solution.
3) done today. Null or empty strings are no longer allowed in reference names.
4) Implement extensible EntityType (ie not enum)
Actually after discussing with Thomas we agreed we don't want this. The model is not
supposed to be extended beyond what is supported by xwiki (ie. objects for example) and if
someone really needs to extend it he won't go through the xwiki model module but
directly through the storage and his own model layer.
Thanks
-Vincent
5) full retest of XE/XEM
6) Move to aspects deprecated methods as much as possible (except those that are required
by Hibernate of course, such as get/SetWeb(), get/setSpace, get/setDatabase, etc). This
means having moved all existing code to not use the deprecated methods anymore.
7) Agree on the need and format for object/property/class references (Anca's mail)
Note that 1), 6) and 7) don't have to be absolutely finished for 2.2 final but the
others do.
Thanks
-Vincent