Hi Erik/Chris - Thanks for the direction. I've heard of Activiti but haven't worked with it yet. Leveraging a specialized for workflow could have some added benefits with a good integration in Apache Isis. In particular, it would be nice to give the domain experts a way to update workflow behavior without involving a developer.
Jeremy D. Branham Tel: **DOTNET -----Original Message----- From: Chris Colman [mailto:[email protected]] Sent: Tuesday, January 06, 2015 3:41 AM To: [email protected] Subject: RE: Workflow Also take a look at Camunda - a fork of Activiti by the main Activiti lead dev. >-----Original Message----- >From: Erik de Hair [mailto:[email protected]] >Sent: Tuesday, 6 January 2015 7:07 PM >To: [email protected] >Subject: Re: Workflow > >Hi Jeremy, > >I've been playing around with Activiti [1]. I thought it would be better >to use an existing specialized package instead of designing my own >workflow model and implement it. > >I've create a proof of concept with several flows and tasks and it does >work, but it looks like there's still a lot of work to do for >interfacing my domain model with the workflow-system (coupling >flows/tasks to my entities, writing Activiti-queries, creating view >models). I'm new to Activiti (or other workflow components) and my >progress isn't that much yet, but I'll let you know if anything >interesting pops up. > >Erik > >[1] http://activiti.org/ > >On 01/05/2015 08:43 PM, Branham, Jeremy [HR] wrote: >> Is anyone using a workflow component in their Isis app? >> JBPM? >> Or do you represent workflow as behaviors in the domain? >> >> What has your experience been? >> >> >> Thanks! >> >> Jeremy D. Branham >> Technology Architect >> >> >> ________________________________ >> >> This e-mail may contain Sprint proprietary information intended for the >sole use of the recipient(s). Any use by others is prohibited. If you are >not the intended recipient, please contact the sender and delete all copies >of the message. >> ________________________________ This e-mail may contain Sprint proprietary information intended for the sole use of the recipient(s). Any use by others is prohibited. If you are not the intended recipient, please contact the sender and delete all copies of the message.
