<cut/> > returning back to HTTP - in camel I have "http.responseCode" header > that works great for me. But in ServiceMix world whenever you have > response code == 500 you have a fault message. In camel it is > extremely easy to handle such response code - in ServiceMix it flows > back and you don't really have a way to catch it somewhere and handle > it properly.
I've just faced the problem described above and I'm looking for some solution. So far I failed.. I have jbi endpoint that is HTTP and this endpoint returns soap fault message I have to transform using XSLT and then merge back with other responses I could receive. I'm looking for a way to handle this fault response, but the only thing that (I believe) should work is writing my own bean that will send the message and handle fault itself - I cannot find any way to handle it using DSL. BTW this is another point in my in/out/fault discussion as if there are no fault messages that behave in a different way the problem wouldn't exist. Do we have any construct we could use to handle it or is it a thing that just should be created? Thanks, Roman
