in a first stage, the interfaces and common abstract classes would be
in the openwfe jar files.
The implementation and extending classes for JCR persistence would be
in the workflow module. Those classes would make use of the magnolia
classes. (they can easily be adapted for a simple and direct JCR access)
At least that's my plan.
The first step is to get John to separate what can be reused from his
implementation.
Once this is done, I will apply it to the JCR using magnolia classes.
This could reasonably be done through next week, and is completely
independent of other tasks and work since it touches just the
workflow module.
Should I enter an item in JIRA ?
Niko
On Sep 7, 2006, at 4:25 PM, Philipp Bracher wrote:
John has a fantastic set of classes for encoding a java bean to
Xml. We're thinking about extending his work so that we can encode
to a set of JCR nodes in the repository.
The proof of concept would be to implement this in the storage of
workitems in the magnolia workflow module.
Yep this is exactly the thing we are looking for. To use Johns
classes would keep the thing out of magnolia, but would still be
related some how. The thing is that Johns implementation would
relay on JCR API (Nodes, Peroperties) where we need to use magnolia
API (Content, NodeData). But if we solve this in a clever way,
means to make this parts pluggable, we could go for it.
We need to discuss how this could get used for the magnolia
multivalue style and similar ;-) Perhaps we should convert the
content so that it fits for such needs.
Then we could see if we can use it in some other places ?
What do the others think ?
GREAT! Nice start anyway!
Philipp Bracher
Niko
On Sep 7, 2006, at 8:34 AM, Nicolas Modrzyk wrote:
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
----------------------------------------------------------------
----------------------------------------------------------------
for list details see
http://www.magnolia.info/en/magnolia/developer.html
----------------------------------------------------------------
----------------------------------------------------------------
for list details see
http://www.magnolia.info/en/magnolia/developer.html
----------------------------------------------------------------
