[HAPI-devel] Testing if a segment is actually in a message

If i do Msg.getNames(), i get a list of all valid segments for that message. However, i'd like to have a list only of the segments that were actually there. The get("SEGMENT") method will create a default segment if it's not there. Is that possible? -

Re: [HAPI-devel] ACK performance

Cool. Will look at it. Thanks for your help James. *Laurent (Harry) Hasson* Co-Founder, 360Fresh.com This email and any attachments thereto may contain private, confidential, and privileged material

Re: [HAPI-devel] ACK performance

Hi Laurent, I think at this point it's safe to say the problem is solved. If you wanted to check it out for yourself, Christian committed the spiffy new ID generators here: https://hl7api.svn.sourceforge.net/svnroot/hl7api/trunk/hapi-mvn/hapi-base/src/main/java/ca/uhn/hl7v2/util/idgenerator/. File

Re: [HAPI-devel] ACK performance

This is good to know. By "next release", do you mean 3.0, or a 2.1? When do you think that would be? I have had similar issues on a project many years ago. The solution we found which worked well in practice was to batch-cache IDs. I am not sure how the IDs for the ACKs are generated though so

Re: [HAPI-devel] ACK performance

Hi Laurent, The main reason for this is that this method assigns a new sequential ID to each ACK message it generates, and it uses a file to keep track of that sequence. That file is read and written on each message, so it is a bit slower than you might think. The next release of HAPI has a great

Re: [HAPI-devel] Customized NACK for badly formatted incoming messages

Hi Laurent, If you make your Application object also implement ApplicationExceptionHandler, there is a callback which will be invoked whenever a parse error occurs. This at least lets you trap the error if you just want to know about it. If what you actually want is a way to not have HAPI choke w

[HAPI-devel] ACK performance

Is there a reason why creating an ACK is so slow? I am calling DefaultApplication.makeACK(_Msh); This takes almost as long as the parsing of the full message coming in which seems counter intuitive. I am on V1.2. -- ---

[HAPI-devel] Customized NACK for badly formatted incoming messages

Hello, I have written a class that extends ca.uhn.hl7v2.app.Application. I have implemented the ProcessMessage() method. I initialize everything as follows: LowerLayerProtocol llp = LowerLayerProtocol.makeLLP(); // The transport protocol PipeParser parser = new PipeParser(new C

Re: [HAPI-devel] Handling HL7 ambiguity in OMG message

I am using 2.0.1 Jens Kristian Villadsen writes: > > > What version of HAPI are you using? -- Everyone hates slow websites. So do we. Make your web apps faster with AppDynamics Download AppDynamics Lite for free tod