Joerg,
OFBiz is in the process of replacing their workflow engine with one of the others listed. I'd be explicit, but it is a work in process and if it doesn't work out, I wouldn't want to be the one starting the rumor.
Ok.
If I'm understanding you correctly about being able to just use the workflow engine, IMO, we're lacking standards for that to be possible. I think a workflow engine by nature typically needs a persistence layer and a service layer.
Of course the result is persisted, but I want to do it, not the workflow engine shall do it. It's just like with Cocoon Forms: the result is also almost always persisted in some way, but I have a form model and with this one I can do what I want. So I want to have a "workflow model", that I want to persist. The requirement simply is, that I need to access the data also independent from the workflow engine and therefore I also want to separate the data model from the workflow engine. Maybe that's possible with OFBiz and I only missed the interface for it.
Given your involvement with Cocoon, do you have any general thoughts about the benefit of using Cocoon and OFBiz together?
Unfortunately not as I only had a quick view into OFBiz and only few experience with workflow at all.
Joerg
--------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
