Mailing-List: contact dev-help@cocoon.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@cocoon.apache.org
content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: text/plain;
	charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
Subject: RE: workflow block commited
Date: Thu, 4 Mar 2004 09:22:14 +0100
Message-ID: <84F0A43A4248CE45B5C0E20F4C40779C5DA85A@naomi.webworks.nl>
Thread-Topic: workflow block commited
Thread-Index: AcP/vOze0ESN9yxMSmuTniGOKVX2HACBL52w
From: "Arje Cahn" <Arje@hippo.nl>
To: <dev@cocoon.apache.org>

Hi Gianugo,
I'm personnaly not the one with the OSWorkflow experience. I'll ask the =
right person to post his experiences. Arje

> -----Original Message-----
> From: Gianugo Rabellino [mailto:gianugo@apache.org]
> Posted At: Monday, March 01, 2004 7:42 PM
> Posted To: Cocoon Dev List
> Conversation: workflow block commited
> Subject: Re: workflow block commited
>=20
>=20
> Arje Cahn wrote:
>=20
> >=20
> >=20
> > I'm interested in a workflow block as well. We currently=20
> have experience using OpenSymphony Workflow and would like to=20
> share this on the Cocoon list.
>=20
> Please do. I'm really interested in that, I don't quite get what all=20
> this workflow fuss is about, so it would be good to know how you're=20
> integrating external workflow engines in a publishing environment.
>=20
> Ciao,
>=20
> --=20
> Gianugo Rabellino
> Pro-netics s.r.l. -  http://www.pro-netics.com
> Orixo, the XML business alliance - http://www.orixo.com
>      (Blogging at: http://www.rabellino.it/blog/)
>=20