You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Various aspects of how Workflow Manager uses Camel can be improved.
Camel's default split and aggregate functionality can be used in multiple places instead of the custom CountBasedWfmAggregator. In places where custom split and aggregate functionality is required, it can be simplified by making better use of exchange properties Camel automatically sets.
Each of the processors in DetectionResponseRouteBuilder get and store the same tracks in Redis. Change it so that the tracks are only retrieved and stored once for the entire route.
TaskAggregationRouteBuilder just uses a single processor so it doesn't need to be its own route.
The text was updated successfully, but these errors were encountered:
Various aspects of how Workflow Manager uses Camel can be improved.
CountBasedWfmAggregator
. In places where custom split and aggregate functionality is required, it can be simplified by making better use of exchange properties Camel automatically sets.The text was updated successfully, but these errors were encountered: