Mailing-List: contact jackrabbit-dev-help@incubator.apache.org; run by ezmlm
Precedence: bulk
Reply-To: jackrabbit-dev@incubator.apache.org
Received-SPF: pass (hermes.apache.org: local policy)
Content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: text/plain;
	charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
Subject: RE: Workflow
Date: Sun, 5 Jun 2005 15:46:56 +0100
Message-ID: <B2467B4F52C33C4FB81F5B5433C3D1AC01E022FB@opexch1.ad.oyster.com>
Thread-Topic: Workflow
Thread-Index: AcVpFh6Un6SZX4k7RSKMv10nLhowxAAwMkCg
From: "Miro Walker" <miro.walker@oyster.com>
To: <jackrabbit-dev@incubator.apache.org>

David,

I=20haven't=20fully=20thought=20this=20through=20yet,=20but=20I=20think=20=
the=20idea=20of
nodetypes=20to=20define=20workflows=20and=20workflowsteps=20would=20be=20a=
=20good=20start=20as
a=20way=20to=20define=20workflow=20templates.=20That=20definition=20would=20=
define=20the
state=20transition=20information=20between=20workflowsteps.=20However,=20i=
t=20may=20be
necessary=20to=20separately=20model=20an=20instance=20of=20a=20workflow=20=
template=20for=20a
specific=20target,=20and=20a=20mixin=20that=20simply=20points=20from=20nod=
es=20to
workflowsteps=20as=20a=20many=20to=20one=20relationship=20might=20not=20be=
=20sufficient=20for
all=20applications.=20

The=20scenario=20I=20have=20in=20mind=20would=20require=20each=20node=20to=
=20(potentially)=20be
in=20a=20different=20state=20for=20multiple=20releases.=20Thus=20a=20node=20=
might=20be
approved=20for=20publication=20in=20Release=201,=20but=20still=20require=20=
approval=20for
Release=202.=20It's=20also=20possible=20that=20multiple=20workflows=20coul=
d=20apply=20to=20a
single=20node=20(e.g.=20standard=20release=20workflow=20vs.=20emergency=20=
release
workflow).

Thus=20the=20mixin=20type=20may=20need=20to=20define=20a=20collection=20of=

workflowstepinstances=20that=20apply=20to=20the=20node,=20where=20each
workflowstepinstance=20would=20define=20the=20state=20of=20the=20node=20wi=
th=20respect=20to
a=20specific=20target.

Does=20that=20make=20any=20sense=20or=20is=20it=20too=20complex=20for=20a=20=
generic=20case?=20Any
comments?

Cheers,

Miro

-----Original=20Message-----
From:=20David=20Nuescheler=20[mailto:david.nuescheler@gmail.com]=20
Sent:=2004=20June=202005=2017:01
To:=20jackrabbit-dev@incubator.apache.org
Subject:=20Re:=20Workflow

hi=20miro,

>=20In=20the=20spirit=20of=20using=20JSR-170=20as=20a=20component=20servic=
e=20in=20a=20larger=20CMS
>=20application,=20has=20anyone=20had=20any=20experience=20with=20open=20s=
ource=20workflow
>=20engines=20that=20could=20be=20integrated=20into=20a=20JSR-170=20based=20=
application?
I've
>=20googled=20a=20bit=20and=20found=20quite=20a=20few=20out=20there,=20but=
=20I=20wondered=20if
anyone
>=20in=20this=20community=20had=20any=20experiences=20(good=20or=20bad)=20=
they=20could=20share?
I
>=20wouldn't=20for=20a=20minute=20suggest=20that=20workflow=20should=20be=20=
built=20into
JSR-170
>=20itself,=20but=20friendly=20co-existence=20could=20be=20very=20useful.
i=20completely=20agree,=20and=20i=20think=20quite=20a=20while=20ago=20we=20=
already=20started
a=20discussion=20about=20that=20on=20this=20list.

my=20personal=20take=20on=20this=20matter=20would=20be:

a)=20have=20a=20couple=20of=20nodetypes=20that=20define=20the=20nodes=20ne=
eded=20to=20
describe=20a=20workflow,=20like=20a=20workflow,=20a=20workflowstep,=20...
with=20anything=20needed=20to=20express=20parallel=20workflows,=20nested=20=
workflows
etc...

b)=20have=20a=20mixin=20"workflowable"=20to=20point=20(using=20references)=
=20to=20the=20the
individual
workflow=20steps,=20to=20refect=20which=20step=20a=20particular=20node=20i=
s=20in=20plus=20a=20set
of
historical=20information.=20i=20think=20this=20would=20allow=20to=20put=20=
any=20node=20into=20a
workflow.

and=20with=20respect=20to=20making=20applications=20interoperable,=20i=20t=
hink=20the
best=20thing=20would
be=20to=20just=20publish=20this=20set=20of=20nodetypes=20somewhere=20(for=20=
example=20in
jackrabbit=20;))
together=20with=20the=20respective=20wrapper=20java=20classes=20to=20manip=
ulate
things...

thoughts?

regards,
david

__________________________________________________________________________=
_______________________________________________
Internet=20communications=20are=20not=20secure=20and=20therefore=20Oyster=20=
Partners=20Ltd=20does=20not=20accept=20legal=20responsibility=20for=20the=20=
contents=20of=20this=20message.=20Any=20views=20or=20opinions=20presented=20=
are=20solely=20those=20of=20the=20author=20and=20do=20not=20necessarily=20=
represent=20those=20of=20Oyster=20Partners=20Ltd.