Am Sonntag, 10. September 2006 13:20 schrieb John Mettraux: > On 9/10/06, John Mettraux <[email protected]> wrote: > > On 9/9/06, Philipp Bracher <[email protected]> wrote: > > > >> Perhaps we should really wait until John was able to make the > > > >> solution A) working. > > > > > > > > I've prepared the code ( > > > > http://svn.sourceforge.net/viewvc/openwfe/trunk/openwfe/openwfe- > > > > applic/src/main/java/openwfe/org/util/beancoder/ > > > > AbstractBeanCoder.java?revision=3241&view=markup > > > > ) : on monday, Nicolas and I will write its JCR extension based on > > > > the current XML extension ( > > > > http://svn.sourceforge.net/viewvc/openwfe/trunk/openwfe/openwfe- > > > > applic/src/main/java/openwfe/org/util/beancoder/XmlBeanCoder.java? > > > > revision=3241&view=markup > > > > ). > > > > > > > > We don't mean to bring an absolute solution, if you people come up > > > > with another, better, solution we'll be glad to support it. > > > > > > I walked through the code and I think this will work quite well. > > Just thought of something : this pair of thread was started by Chris, > who simply wanted to unleash the dialog + workitem power.
Yes I did. I want to use the workflow engine to push a payload/content node/envelope/tree or similar around a team so that they can prepare some information that in a final step will be used to create a page. This page will then be further worked on in the normal fashion to prepare the page for publication. > > Now we're working on a BeanToJcr (JcrBeanCoder) that turns any java > instance that follow the 'bean convention' into a JCR 'branch'. > > While OpenWFE workitems do follow the 'bean convention', our real > requirements are (please correct me if I'm wrong) to have workitem id > and payload at hand easily. Yes easily at hand is what I am looking for. I assume my workflow represents a structured process of gathering/altering/creating information, and that I need to access that information as part of the workflow. If I understand the owfe api correctly I should store all of my information as attributes on a workitem. The Activation workflow works around the separation of the workflow item and its page. Specific fields like path, start date, and end date are explicitly copied into the workflow from the nodes meta data, so that the engine has access to those values, and doesn't reference directly the ones stored in the page. Under that model, you'd update the page to publish, and expect that the workflow item was updated. ---------------------------------------------------------------- for list details see http://www.magnolia.info/en/magnolia/developer.html ----------------------------------------------------------------
