Hi John,
the embedded engine is just an engine. The getLaunchables() thing is
about mapping worklist users to flows they may launch. As there are no
"worklist users" in an engine, there are no "launchables".
I guess you're integrating within Magnolia, you could delegate this
getLaunchables() to Magnolia by having a list of JCR stored process
definitions that are actually readable by the user triggering the job.
Would that do it ?
Haaa well, sure. Now I've paused for a bit, I can see that makes
perfect sense ! Thanks !
Another concern I had (and I'm sure I'll have a few more questions
later on;)) is about locking. Currently, in some situations, we do
getAndLock for retrieving workitems. How can I do something similar
with the embedded engine? The doc states that "no workitem locking is
currently provided by embedded worklists, you have to handle it on your
own". That sounds fair enough, but could you elaborate a little bit on
how/why? I assume I can't do something as simple as in-memory locking,
since my engine is persistant... I'm kind of unconfident in this area,
as you can see, and would appreciate any tip ;)
Thanks again.
g
--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google Groups "OpenWFE
users" group.
To post to this group, send email to [email protected]
To unsubscribe from this group, send email to [EMAIL PROTECTED]
For more options, visit this group at
http://groups.google.com/group/openwfe-users?hl=en
-~----------~----~----~----~------~----~------~--~---
