25 Jun
2008
25 Jun
'08
1 a.m.
Hi, Vincent.
Sorry for late reply.
Vincent Massol wrote:
It seems like you're transforming current storage
code into
components. I'm not sure what important advantages this brings. What
I'd like to see is to have new code and new apis use components but
I'm not sure about old code. Maybe you could explain what's your plan?
The plan is in proposal "Componentize XWiki Stores"
http://xwiki.markmail.org/message/vs7wbfjv7ipyz2t3 and XWIKI-2443
I don't see anything wrong in components in old code.
Do you plan to create clean interfaces for storage?
not yet.
I just want to refactor old storage system for easy support of many
storage implementation. Current store system contains too many code
duplication (business code, manipulate with model) for different storage
implementations. And I want to separate simple DAO components (which can
be used as prototype for new storage components) from old stores to
resolve it.
If so this really
needs to be discussed and proposed on the devs list with a design page
on xwiki.org.
However this probably requires a prerequisite of having the new model
in place before it can be started? wdyt?
Yes for new storage component.
So the question I have is: should I completely rewrite storage system (+
new model) from scratch just for add a good jcr storage :) or can I just
refactor old one?
New storage is better of course. But it requires so much work,
especially on new model.
When new data model is planed?
--
Artem Melentyev