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: domain of edgarpoce@gmail.com
 designates 64.233.170.197 as permitted sender)
DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws;
        s=beta; d=gmail.com;
        h=received:message-id:date:from:user-agent:x-accept-language:mime-version:to:subject:references:in-reply-to:content-type:content-transfer-encoding;
        b=m7vvf0LSXeE/JU5M4rR3xQC+tWwa0nBKgm30Lk6GAN2oSiUZZ+ZiAlh75kNBwi1GiL/aPfZOf01I6L+CWeSTdhih5gP+EtkzCm9VrArV9UEmPb3y47gHMtTmh1tk3kGtef9JGGA0VwD581pmsNQm6/nJxgU9Go/dlqvTduSy5aY=
Message-ID: <42A3353B.3030803@gmail.com>
Date: Sun, 05 Jun 2005 14:24:11 -0300
From: Edgar Poce <edgarpoce@gmail.com>
User-Agent: Mozilla Thunderbird 1.0 (Windows/20041206)
MIME-Version: 1.0
To: jackrabbit-dev@incubator.apache.org
Subject: Re: Workflow
References: <B2467B4F52C33C4FB81F5B5433C3D1AC01E022FC@opexch1.ad.oyster.com>
In-Reply-To: <B2467B4F52C33C4FB81F5B5433C3D1AC01E022FC@opexch1.ad.oyster.com>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit

hi Miro

There's an archive at 
http://dir.gmane.org/gmane.comp.apache.jackrabbit.devel

regards
edgar

Miro Walker wrote:
> That sounds like a good idea - some idea of quasi-standard approaches to
> certain applications would be very useful I would imagine. I'd like to
> have a look through the archives to find the earlier conversation - is
> there a searchable version of the mailing list archive or do I need to
> download the tarballs and search them offline? The only place I've seen
> is: http://incubator.apache.org/mail/jackrabbit-dev/.
> 
> Cheers,
> 
> Miro
> 
> -----Original Message-----
> From: Gregor J. Rothfuss [mailto:gregor@apache.org] 
> Sent: 05 June 2005 17:53
> To: jackrabbit-dev@incubator.apache.org
> Subject: Re: Workflow
> 
> 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.
> 
> _________________________________________________________________________________________________________________________
> Internet communications are not secure and therefore Oyster Partners Ltd does not accept legal responsibility for the contents of this message. Any views or opinions presented are solely those of the author and do not necessarily represent those of Oyster Partners Ltd.
>