OK - then I don’t think you’ll ever get that body from a real system when you’re using Camel (unless you do something to make it happen).
Two of the components that support MLLP (camel-mina2, camel-netty4) do NOT parse/convert the message by default - they just wrap the payload in the MLLP envelope. Then you’d use a data format to convert the payload to some type of object. The data format would probably throw an exception if it couldn’t parse the payload (camel-hl7 does) The camel-mllp component is a little different - it does parse the message in order to set some message properties. It will also throw an exception if it can’t understand the message. So I think what you’re after is an error handler in the case of an invalid message - is that correct? And what version of Camel are you using? > On May 17, 2016, at 7:49 AM, sekaijin <jean-yves.terr...@aphp.fr> wrote: > > I'm not sure that the body is equal to "error decoding HL7" > > I'm using mina and hl7 to implément mllp protocol. > > > A+JYT > > > > -- > View this message in context: > http://camel.465427.n5.nabble.com/choice-when-not-working-as-expected-in-the-camel-route-tp5782452p5782701.html > Sent from the Camel - Users mailing list archive at Nabble.com.
