Guillaume Nodet wrote:
> Yes, i had considered that...
> The problem is that with an In-Out mep, the consumer is waiting for a
> response. What could we send ?
If a request comes through then all is ok, if a request if filtered out one
could throw an exception, which would roll back this message exchange?
OK: Req --> Fil --> Req
Resp <-- ter <-- Resp
NOK: Req --> Fil
Err <-- ter
If the calling component is a endpoint e.g. HTTP then this would anyhow return
some HTTP status code
Maybe my view is too simplistic, not knowing the details of the implementation
or even the JBI spec very good, but that would have been my expectation.
Or why not make it configurable, if the property is true this behaviour,
otherwise you return an error too as today that an inout is not allowed with
this configuration. If you look at it from this side, you return a error now as
well, so ...
And apart from the pipeline this would otherwise be the only routing pattern
that does not support InOut but would be very usefull if one would have it.
Just my 5 cents,
Peter
