Miro Walker wrote:
I haven't fully thought this through yet, but I think the idea of
nodetypes to define workflows and workflowsteps would be a good start as
a way to define workflow templates. That definition would define the
state transition information between workflowsteps. However, it may be
necessary to separately model an instance of a workflow template for a
specific target, and a mixin that simply points from nodes to
workflowsteps as a many to one relationship might not be sufficient for
all applications.
would that be one of the situations where jackrabbit could document
commonly used node types? i remember a discussion about that a while ago.
