On Thu, Mar 31, 2011 at 4:24 AM, John Mettraux <[email protected]>wrote:
> > It could work. It sounds like an idea to explore. > > Another idea would be to use ruote-sequel (or ruote-dm) for normal ruote > operations and an active-record model for workitems. Somehow a rails > application interacts mostly with ruote via the engine's launch/cancel > methods and the engine.storage_participant methods (for workitems). You > could bypass the storage_participant and use the active-record model for > workitems (to query for workitems)... Ah wait, you'd still need the reply > method to use active-record and not sequel... Not so straightforward. > > Hi John, thanks for the feedback! Our current strategy was to override the StorageParticipant, and create/update own Workitem AR model in the actions available. I'm keeping a workitem's history in our model, but hopefully, we can sync the two models this way. But it does seem redundant. I've attempted to use ruote-sequel, but it blocks on a call to engine.register which I'll still need to investigate [may be sequel/mysql related]. Currently using the FsStorage, but I guess it won't work on linux/NFS (shared with two machines). > Maybe we need a ruote-activerecord for ruote > 2.2.x it would be very useful for rails projects. I was looking through the ruote-sequel code to see the work required. but I'll need to become acquainted with the ruote model first. still learning about fei, wfid & other here ;) best regards, Pedro -- you received this message because you are subscribed to the "ruote users" group. to post : send email to [email protected] to unsubscribe : send email to [email protected] more options : http://groups.google.com/group/openwferu-users?hl=en
