Hi there, Now that I've gotten more to grips with ruote-rest, I'm interested in some ways it can be extended. Part of the complexity of my workflow comes from having participants that may not be currently defined within the scope of a given engine.
What would you think if I extended the XML participant element to be able to specify "external" participant code - be it a GEM, a ruby source file, yaml etc referenced by URL or similar? Obviously there are some serious trust issues involved in doing this, but it does allow ruote-rest to be much more flexible in its acceptance of workflow documents. Regards, Corin --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "OpenWFEru 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/openwferu-users?hl=en -~----------~----~----~----~------~----~------~--~---
