There is a new exchangeProperties in the model json files. If an EIP has no support then there are no exchangeProperties at all in the json.
Also notice that Aggregate is special as it has 3 consumer (input) that end user can set to control the EIP. All the others are producer based, eg output so they come after the EIP when being routed.
For example the CamelAggregatedCompletedBy that tells the user how the exchange was completed (size, timeout etc.)
Please describe the feature that you want to propose
https://issues.apache.org/jira/browse/CAMEL-20381
For example Aggregate EIP https://github.com/apache/camel/blob/main/catalog/camel-catalog/src/generated/resources/org/apache/camel/catalog/models/aggregate.json#L47
There is a new exchangeProperties in the model json files. If an EIP has no support then there are no exchangeProperties at all in the json.
Also notice that Aggregate is special as it has 3 consumer (input) that end user can set to control the EIP. All the others are producer based, eg output so they come after the EIP when being routed.
For example the CamelAggregatedCompletedBy that tells the user how the exchange was completed (size, timeout etc.)