Is Kepler planned to add the ability to create dynamic workflows determined by the output of rules engines such as Drools or Esper? I would like the ability to be able to let Kepler choose from a set of static workflows for individual xml files based on the data in the xml file. Here is a short description of the use-case:
1) An xml file is recieved by a generic Kepler workflow. 2) An Actor looks into the xml file for specific fields and passes that information to a rules engine. 3) The rules engine determines the specific workflow to send the xml file to, or conversely the rules engine determines the specific actors and edges to determine the optimum workflow for the file. 4) Kepler routes the file through the workflow or actors defined by the rules engine. This functionality mirrors the Dynamic Routing Slip enterprise integration pattern. Can Kepler do this now, or is it planned in the near or long term?
_______________________________________________ Kepler-users mailing list Kepler-users@kepler-project.org http://lists.nceas.ucsb.edu/kepler/mailman/listinfo/kepler-users
