A) We store the workitems in the magnolia way (same structure as
paragraphs) this allows to use the dialogs to manipulate them
(currently they are stored unfortunately as plain xml)
Nicolas & John: what do you think about A) should we enforce that?
I think there are other use-cases where we would like to have that
I don't really remember what the structure for paragraph is, but I
think it would be good to have an API to persist java objects to the
JCR, generically. (hibernate for JCR ?)
We have a couple of examples in magnolia I guess:
- users
- roles
- groups
- workitems
Also in my code here, I also need to persist some searches object
(that I'm doing just the same dirty way; serialize to xml..)
I get the feeling it would not be to hard for us to define a generic
API, and for me and John to implement it.
What do you think ?
Niko,
----------------------------------------------------------------
for list details see
http://www.magnolia.info/en/magnolia/developer.html
----------------------------------------------------------------
