Tim Williams wrote:
Workflow means a lot of different things to different people,
could you specify a bit more what you mean?
I'm thinking something fairly simple. I'm clearly no expert in either
CMS or WFE's so my terminology coule be a bit off but something like:
o) A document has multiple "states" -- new, in-edit, in-review, published
o) A simple "routing" logic associated with child nodes of the "site"
element of site.xml in Forrrest.
o) Obviously some sort of permissions associated with the routing
logic above (e.g., person X has the ability to create new content and
Person Y can "publish" that content.
That's similar to what the Cocoon Flowscript implemented solution I
mentioned do, but this is unfortunately not freestanding enough to
package as a separate workflow handling so I can't help you with code
(and I guess you are not using Flowscript as controller logic anyway).
But just to get you started: it's not much code reuqired to implement
something like this on your own on top of Slide.
Slide kernel gives you all the access control you need and since
repository nodes in Slide can have arbitrary properties, you can easily
define your own property for workflow state, preferrably outside of the
DAV: namespace.
You also mentioned a notification scheme, which would of course also
have to be implemented by something else than Slide.
I've got a rough idea of what's needed but flexible enough to use
what's out there (if anything).
Unfortunately I don't have any good links to existing simple
workflow engines, I would be as interested as you in any hints!
At my day-job company we have a CMS using Slide as repository impl
and Cocoon as presentation engine. This particular CMS uses Cocoon
Flow-script for the controller logic and the workflow processing
is mostly implemented in Cocoon Flow (with some sanity checks
in the Java Repository integration code on top of Slide).
Can I ask what CMS you use on top of Slide at work?
Sure; it is a custom open source integration project initially done
for a Swedish government body. The recepient has not yet decided if
they want to donate the integration bits back as open source.
(Sorry, I know that's not what you wanted to hear.) ;-)
Regards,
Martin
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
