next time :-)
We were using the NoValidation validation context which has let us get
away with no minute test cases in the past.
Sorry for the confusion.
-Mike
On 3/11/2020 10:10 am, Mike Mills wrote:
I have been working a lot with DT and TS fields in Hapi.
If you create a default
I have been working a lot with DT and TS fields in Hapi.
If you create a default ADT_A01 message and attempt to set a new MSH-7
value it will throw a DataTypeException if that field is not fully
populated with fields of Year through to Seconds.
In the API documentation it states that the fiel
Craig, Jim,
The simplest way you could get an Index out of bounds is most likely due to
the *theDefinitionPath *variable being empty (ie get element 0-1=-1). I
would doubt that this is a concurrency issue.
I have encountered several issues with Hapi not keeping track of the
underlying field indic
Hi,
we have had an interface in production fail when we try to create a new
message and call .initQuickstart().
What is happening is the id_file is read and the value is coerced into a
number. Unfortunately the code uses an Int (10 chars long, max
value 2147483647) so once the value in the id_fil
arator (in my example this fails as
'&' is found instead of '|').
Sorry for the false alarm.
Kind regards,
-Mike
On 28 July 2017 at 14:38, Mike Mills wrote:
> I have been attempting to convert our routing code to use the more
> performant PreParser over a full Pipe
I have been attempting to convert our routing code to use the more
performant PreParser over a full PipeParser.
I have found this message to throw an exception in the pipe parser, but no
exception is thrown with the PreParser:
MSH|^~\\&|20161024182512||ORM^O01|1624|T|2.4||8859/1
Note th
chieve version-specific validation, then parse it again with a
> context using CanonicalModelClassFactory with validation disabled to get
> the data “de-serialized” and work with. It will obviously not be efficient,
> but at least it’s a work-around.
>
>
>
> -Craig
>
>
’s why it takes more time
> and resources.
>
>
>
> Christian
>
>
>
>
>
> *Von: *Mike Mills
> *Gesendet: *Freitag, 30. Juni 2017 03:59
> *An: *Christian Ohr
> *Betreff: *Re: [HAPI-devel] Hapi parse performance.
>
>
>
> Christian,
>
As part of fuzz testing it has been identified that strange combinations of
MSH-9 can cause some quite unexpected behaviour.
In this example a message defined as ADT^M02 was routed as an MFN^M02 due
to routing only checking MSH-9-2 and ended up being processed as a
V24.GenericMessage.
So my quest
Hi,
Are the any efforts being made to improve the performance of parsing an hl7
message?
I am considering dropping parsing of messages using hapi because of the CPU
load and memory requirements.
It seems like Hapi parses like a DOM parser as it goes though the entire
message.
It would be good i
James,
You could automate the XP to Linux step with Jenkins. Use a remote agent on
the XP machine for the first part, the the output of that build can be
automatically fed as the input of the Linux build.
You could also run a VM on the Linux box with an XP image of you want to
save on hardware.
James,
I work with David and have been working with him to get to the bottom of
the issue so that we can choose a suitable solution for us.
We noticed that some validation is turned on when you use the pipeParser
but not when you use the parse() on a Message. eg:
String msh_string =
"MSH
Hi,
I have found a wierd case where calling .encode() on a Hapi message can end
up changing the number of reps returned by the Message object
This code shoudl print out the same console output before and after the
.encode call.
Unfortunately calling .encode() causes some of the reps to indicate
Have you tried using initQuickstart() on the adt object?
We only use std mllp (ie not over http) but having gone through the receive
code for mllp, you must have MSH9 set, which is one of the fields
initQuickstart configures.
The content type error could just be a side effect of not sending a val
I forgot to CC the list in the response...
-- Forwarded message --
From: Mike Mills
Date: Sat, Feb 20, 2016 at 7:18 AM
Subject: Re: [HAPI-devel] (no subject)
To: "Davies, Brian"
Your client is sending to "Integer.parseInt(env.getProperty("http.port
Have you ever thought about a baseclass for MSH that is independent of
structure?
This would make creating AppRoutingData much easier.
So in ca.uhn.hl7v2.protocol.impl.ApplicationRouterImpl#findApplication
where a terser is used to extract msh fields, you could replace this with a
get("MSH") whe
. I've removed it from the repo and also applied your correction to
> the readerinputstream. With those two changes, the tests all pass for me.
> Can you give it a whirl? (and thanks for the fix!)
>
> Cheers,
> James
>
> On Mon, Sep 8, 2014 at 12:49 AM, Mike Mills wrote:
>
Hello,
I have just checked out hapi-testpanel and tried to compile/test.
The test code fails to compile for
class ByteCapturingMinLowerLayerProtocolWrapperTest.
It is missing the org.openide.util.io.ReaderInputStream class.
A simple code change of line 53 from
InputStream iis = new ReaderInpu
18 matches
Mail list logo
