incubator-jspwiki-user mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Andrew Jaquith <andrew.r.jaqu...@gmail.com>
Subject Re: Wiki Workflow
Date Wed, 25 Feb 2009 15:01:08 GMT
It's not implemented in 3.0 yet. Shouldn't be too hard, but it will
come later rather than sooner in the 3.0 dev cycle, barring someone
else tackling it first. I'm waist-deep in the JSP migration right
now....

Andrew

On Wed, Feb 25, 2009 at 9:25 AM,  <Louis.Masters@log-net.com> wrote:
> Andrew:
>
>>>The bad news is that we don't
>>>yet have a way to persist workflows between webapp restarts. That's
>>>going to change in JSPWiki 3, when we will begin requiring all objects
>>>involved in workflows to be Serializable.
>
>
> I know we spoke about this a month ago, but could you point me to where
> this is in the 3.0 codeline?  I would like to try to migrate it into 2.8
> (unless 3 is due out soon).
>
> Thanks,
> Lou
>
>
>
>
>
> Andrew Jaquith <andrew.r.jaquith@gmail.com>
> 02/25/2009 09:07 AM
> Please respond to
> jspwiki-user@incubator.apache.org
>
>
> To
> jspwiki-user@incubator.apache.org
> cc
>
> Subject
> Re: Wiki Workflow
>
>
>
>
>
>
> Hi Nicola --
>
> The page you referenced is not the documentation for workflows, just a
> wiki page. For the real documentation, take a look at the Javadoc for
> the workflow API.
>
> "Workflows," as they exist today, are comprised of two things: 1) a
> Workflow.jsp page, which provides an "inbox" that allows users to
> respond to workflow decisions and notifications, and 2) an API that
> allows participating classes to create the workflow objects
> themselves.
>
> To date, there are only two out-of-the-box workflows: for approving
> edited pages, and for approving new user accounts. Both of these can
> be configured via jspwiki.properties. These are both single-approval
> models.
>
> Multiple-approval models, like the one you described, are definitely
> possible using the workflow APIs, but not implemented in any
> out-of-the-box workflows today. You'd need to write Java code that
> links together the correct steps and decisions. I'd recommend you take
> a look at the WorkflowBuilder class, and the various workflow test
> classes, to see how we've done the others.
>
> If you are feeling super-motivated, we'd love to get some
> contributions. It would be great to have a "multi-approval" builder
> method in WorkflowBuilder.
>
> The good news is that the classes, from the Java perspective, are
> fairly simple and easy to understand. The bad news is that we don't
> yet have a way to persist workflows between webapp restarts. That's
> going to change in JSPWiki 3, when we will begin requiring all objects
> involved in workflows to be Serializable.
>
> Andrew
>
> 2009/2/25 Fischer, Nicola (ORISA Software GmbH) <fischer@orisa.de>:
>> Hi,
>>
>> I was looking into the workflow plugin but I ist hard to understand it
> form the documentation:
>> http://www.jspwiki.org/wiki/WorkflowEvent
>>
>> And the Page
>> http://www.jspwiki.org/wiki/WorkflowPlugin has an error.
>>
>> I would like to know if there is something like multipple approval.
>>
>> Say i have a Document or Page and I want it to be approved by every
> member of a group. And these members should even get a notification that
> there are open approvals.
>>
>> Can JSPWIKI Workflow do this or do we need to implement it?
>>
>>
>> Mit freundlichen Grüßen
>> Nicola Fischer
>> Entwicklung & Controlling
>> ___________________
>> ORISA Software GmbH
>> Humboldtstr. 13
>> 07743 Jena
>>
>> Amtsgericht Jena HRB 204876
>> Geschäftsführer: Dr. Georg Elsner
>>
>> telefon: +49 (0)3641-2844 59
>> telefax: +49 (0)3641-2844 22
>>
>> internet: http://www.orisa.de
>> email: mailto:fischer@orisa.de
>>
>> Diese E-Mail enthält vertrauliche und/oder rechtlich geschützte
> Informationen. Wenn Sie nicht der richtige Adressat sind oder diese E-Mail
> irrtümlich erhalten haben, nformieren Sie bitte sofort den Absender und
> vernichten Sie diese Mail. Das unerlaubte Kopieren sowie die unbefugte
> Weitergabe dieser Mail ist nicht gestattet.
>> This e-mail may contain confidential and/or privileged information. If
> you are not the intended recipient (or have received this e-mail in error)
> please notify the sender immediately and destroy this e-mail. Any
>> unauthorized copying, disclosure or distribution of the material in this
> e-mail is strictly forbidden.
>>
>>
>> ____________
>> Virus checked by G DATA AntiVirus
>> Version: AVF 19.276 dated 25.02.2009
>>
>
>

Mime
View raw message