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
This singleton will be for listening to the single JMS queue. It will be a
Spring bean, which is a singleton by default anyway. The fewer objects I have
to recreate for each message, the more efficient it should be. Singletons are
usually designed to be accessible by multiple threads, but in thi
If I recall correctly a singleton is a class that is available across the
entire jvm, so if you intend it to handle all messages from lots of queues,
I'd think it might quickly become a bottleneck for messaging. No expert in
this but, from an integration perspective it would be more scalable a
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
4 matches
Mail list logo
