You are welcome. Hope it was useful.
You don't really have much choice but to parse the message or you can't do any
work on it in HAPI. That's how IEs do it anyway.
Stewart
___
Hl7api-devel mailing list
Hl7api-devel@lists.sourceforge.net
https://list
-devel
Sent: Thursday, February 8, 2024 1:54 PM
To: hl7api-devel@lists.sourceforge.net
Subject: Re: [HAPI-devel] Thread Safe Queue for HL7 messages
CAUTION: This email originated from outside of the organisation. Do not click
links or open attachments unless you recognise the sender and know the conte
i-devel
mailto:hl7api-devel@lists.sourceforge.net>>
Sent: Thursday, February 8, 2024 1:54 PM
To:
hl7api-devel@lists.sourceforge.net<mailto:hl7api-devel@lists.sourceforge.net>
Subject: Re: [HAPI-devel] Thread Safe Queue for HL7 messages
CAUTION: This email originated from outside of the o
I have a follow-up question. The documentation says that HapiContext is not
intended to be a singleton. Should it be fine to create one HapiContext in the
singleton that I create to handle the incoming messages from my queue? It seems
very inefficient to recreate the objects I need to send each
Thanks for the feedback, Mike and Stewart. I use JMS message queues in other
parts of the application. I had thought of that as a possible design. I wanted
to check that I wasn't overlooking an existing solution and reinventing the
wheel.
Thank you,
Patrick R. Thomas
Haven't used HAPI in the raw for a while now, but I think it is focused on the
serialisation of HL7, there is an MLLP Sender/receiver, but if you want to
write then to a queue, after or before receipt/send, you'd need to handle the
queue yourself. JMS or ActiveMQ/Rabbit etc. There are tons
6 matches
Mail list logo
