Skip to main content

Notice: This Wiki is now read only and edits are no longer possible. Please see: https://gitlab.eclipse.org/eclipsefdn/helpdesk/-/wikis/Wiki-shutdown-plan for the plan.

Jump to: navigation, search

Difference between revisions of "SMILA/Specifications/RecordWorkflowDiscussion09"

Line 1: Line 1:
=Problems=
+
=Wanted=
  
 
# it's wanted to have ability to filter record in Router/Listener before starting any operations
 
# it's wanted to have ability to filter record in Router/Listener before starting any operations
 
# it's wanted to configure ODEWorkflowProcessor with record-filter used.
 
# it's wanted to configure ODEWorkflowProcessor with record-filter used.
  
 
+
=Suggested=
 
== WorkflowProcessor ==
 
== WorkflowProcessor ==
 
=== Problems ===
 
=== Problems ===

Revision as of 11:01, 17 November 2008

Wanted

  1. it's wanted to have ability to filter record in Router/Listener before starting any operations
  2. it's wanted to configure ODEWorkflowProcessor with record-filter used.

Suggested

WorkflowProcessor

Problems

Now WorkflowProcessor API accepts series of Ids only for starting pipelines.

public interface WorkflowProcessor {
  ...
  Id[] process(String workflowName, Id[] recordIds) throws ProcessingException;
  ...
}

ODEWorkflowProcessor implementation is reading property "record.filter" from it's own configuration file and filtering all records before processing with only one filter.

Suggested

To configure record filter in Router/Listener rules

WorkflowProcessor public API should accepts record or Id + filterName.

public interface WorkflowProcessor {
  ...
  void process(String workflowName, record) throws ProcessingException;
  ...
}

Or

public interface WorkflowProcessor {
  ...
  void process(String workflowName, Id id, filterName) throws ProcessingException;
  ...
}

Back to the top