418 [main ] ERROR DefaultErrorHandler
- Failed delivery for (MessageId:
ID-giuliano-Latitude-E6540-37043-1503395640049-0-7 on
ExchangeId:ID-giuliano-Latitude-E6540-37043-1503395640049-0-5). Exhausted
after
delivery attempt: 1
caught: org.apache.camel.component.file.GenericFileOperationFailedException:
Cannot
store file: data/asd
org.apache.camel.component.file.GenericFileOperationFailedException: Cannot
store file: data/asd
...
Caused by: org.apache.camel.InvalidPayloadException: No body available of
type: java.io.InputStream but has value: [a, b] of
type: java.util.ArrayList
...
So in order to correct my error I changed the implementation of
the aggregation strategy returning an exchange with the IN instead of
the OUT, but I have a few questions:
- Is the missing pipeline-triggering inside the aggregator subroute a bug
or a desired feature?
- Is it correct to implement an aggregation strategy returning an exchange
with OUT ?
Thanks,
Giuliano Santandrea
main ] ERROR DefaultErrorHandler
- Failed delivery for (MessageId:
ID-giuliano-Latitude-E6540-37043-1503395640049-0-7 on ExchangeId:
ID-giuliano-Latitude-E6540-37043-1503395640049-0-5). Exhausted after
delivery attempt: 1 caught:
org.apache.camel.component.file.GenericFileOperationFailedException:
Cannot store file: data/asd
org.apache.camel.component.file.GenericFileOperationFailedException:
Cannot store file: data/asd
...
Caused by: org.apache.camel.InvalidPayloadException: No body available
of type: java.io.InputStream but has value: [a, b] of type:
java.util.ArrayList
...
So in order to correct my error I changed the implementation of the
aggregation strategy returning an exchange with the IN instead of the
OUT, but I have a few questions:
- Is the missing pipeline-triggering inside the aggregator subroute a
bug or a desired feature?
- Is it correct to implement an aggregation strategy returning an
exchange with OUT ?
Thanks,
Giuliano Santandrea
