Thanks for comments.
@cstewart hawk eye 😉 the pipeline obviously fails before pseude-async can execute. JSON formatter intentionally causes an error, as described. SInce the generator is before the formatter, I would assume, it would be executed first. It is clearly NOT the case.
@Supratim It is router with both ‘true’ routes. Thank you for your suggestion. Of course you can introduce some magical checks first, but this is exactly try-and-catch approach i want to avoid, since JSON is not schema-first approach.See scenario below…
Hence my query again:
what is the proper way to design an asynchronous behaviour.
What i mean by that is the following:
A sender POSTs a JSON message to SL.
SL pipeline.accepts the JSON payload, sends HTTP 200 back to the sender, indicating, it has taken the data.
Whatever happens with the data in the pipeline is SL’s business.
cheers
Simon 🙂
