cocoon-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Steele, Tony" <>
Subject RE: Why does Action extend ThreadSafe ?
Date Thu, 09 Aug 2001 15:16:01 GMT
On this issue I agree with Sylvain. We used actions to implemented an
interface to our workflow engine , the action sends an event to the workflow
engine which the returns a page (which is then processed by the pipeline).
However we did not appreciate the restrictions at that time, i.e. it has to
be threadsafe. Although the Action seemed the perfect mechanism to interface
to something like a workflow engine, it's current limitations would seem to
restrict it to very simple use.

Can any body suggest an alternative method to using an Action of interfacing
to a workflow engine. 

Tony Steele

> So I propose to modify the sitemap so that Action, Matcher 
> and Selector
> are handled as regular components and properly released. Once this is
> done, ThreadSafe will be removed from Action, and moved on relevant
> Action implementations.
> +1 from me :)

Knowledge by Experience

To unsubscribe, e-mail:
For additional commands, email:

View raw message