camel-users mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Christian Ohr <christian....@gmail.com>
Subject Re: HL7 v. 2.7 with mina2
Date Tue, 14 Jan 2014 08:57:52 GMT
In fact, HAPI does not yet support HL7 v2.7, so you will receive an
exception as soon as you parse such a message.

Mina itself is unaware of HL7 versions; the hl7codec just unpacks the
message payload from the MLLP wrapper. The error message indicates that the
trailing bytes of a MLLP frame are missing.

regards
Christian



2014/1/13 giandrea77 <andrea.girardi@gmail.com>

> Hi there,
>
> Our customer changed the HL7 message format from 2.3 to 2.7 and I having
> some issue with new message format. Basically we was able to route message
> using mina2 protocols in this way:
>
> <route>
> <from
> uri="mina2:tcp://
> 10.124.199.40:2575?sync=true&amp;codec=#hl7codec&amp;minaLogger=true"
> />
> [...]
> </route>
>
> and it worked fine untile the upgrade of message standard. Indeed, changing
> the format from 2.3 to 2.7 it doesn't work, we get this DEBUG message:
>
>  2014-01-09 08:36:40,717 DEBUG HL7MLLPDecoder [104]  - Start scanning
> buffer
> at position 0
>  2014-01-09 08:36:40,718 DEBUG HL7MLLPDecoder [56]  - No complete message
> in
> this packet
>
> We are using HAPI as message parser and I'm afraid it should be the problem
> but, in this case, what I'm expecting is that Camel should be able to route
> the message though mina2 and, when we read HL7 message from our business
> classes catch an exception. But it doesn't, it seems that mina2 is not able
> to routes the message.
>
> Any clue with that?
>
> thanks,
> Andrea
>
>
>
> --
> View this message in context:
> http://camel.465427.n5.nabble.com/HL7-v-2-7-with-mina2-tp5745900.html
> Sent from the Camel - Users mailing list archive at Nabble.com.
>

Mime
  • Unnamed multipart/alternative (inline, None, 0 bytes)
View raw message