Hi Jeremy, I think that Oscar's app has used JBPM, so he might have some thoughts.
We don't use any workflow in the Estatio app, but on the other big (.NET) Naked Objects project that I work on we use BizTalk quite extensively, along with a Task object. The rule of thumb we employ there is: * if the end-user can perform the business operation immediately, without having to collaborate with anyone else, then don't introduce workflow * if the business process is more complex and executes "over space", by which I mean it involves several end-users collaborating together, then use the Task object as a token for passing around work. Isis' BookmarkService [1] is a good way to hold polymorphic references to arbitrary domain objects * similarly, if the business process executes "over time", eg a reminder to renew an insurance policy or some such) then again, use the Task object and use a scheduler [2, 3] to bring it back into an end-users in-tray when the task becomes due. Hope that helps Dan [1] http://isis.apache.org/reference/services/bookmark-service.html [2] http://isis.apache.org/reference/non-ui/background-command-execution.html [3] https://github.com/danhaywood/isis-module-scheduler On 5 January 2015 at 19:43, Branham, Jeremy [HR] < [email protected]> 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. >
