RE: [HAPI-devel] IndexOufOfBoundsException

[Tripp, B. <Bry...@uh...>]

Hi William, 

Thanks, someone else pointed out the same bug a few days ago.  It's fixed in
HEAD, so let me know if you would like an interim build without this
problem.  

HL7 defines only 2 components for UB2-6, so when you have content (e.g. two
spaces) in component 6, HAPI's handler for "extra components" kicks in, and
the bug was in this code, for the case when a populated extra component
follows an empty extra component.  Messages that adhere strictly to the HL7
spec should work fine, as should most messages that don't.  At UHN we
haven't yet used HAPI 0.4 in a high-volume scenario, but we have parsed
perhaps 2000 test messages without any trouble.  

Bryan 

> -----Original Message-----
> From: William Butler [mailto:wb...@pa...]
> Sent: December 2, 2003 10:07 PM
> To: hl7...@li...
> Subject: [HAPI-devel] IndexOufOfBoundsException
> 
> 
> Some feedback here: I tried running TestPanel with some HL7 data from 
> my institution but I didn't get far. I get the message 
> "IndexOutOfBoundsException index 3 size 0". By deleting lines 
> one at at 
> time from the HL7 message I isolated the line
> 
> UB2|||~~~~~~|||^^^^^  ^^^^^^^^^^^^^^|^^^^^^^^^^^^^^^|^^^^^^^^
> 
> as the cause. In particular, deleting the two whitespaces  
> between the 
> ^ characters before feeding the message causes TestPanel to function 
> fine.
> 
> Thanks,
> 
> Bill Butler
> 
> Mass General Hospital
> 
> 
> 
> -------------------------------------------------------
> This SF.net email is sponsored by OSDN's Audience Survey.
> Help shape OSDN's sites and tell us what you think. Take this
> five minute survey and you could win a $250 Gift Certificate.
> http://www.wrgsurveys.com/2003/osdntech03.php?site=8
> _______________________________________________
> Hl7api-devel mailing list
> Hl7...@li...
> https://lists.sourceforge.net/lists/listinfo/hl7api-devel
> 


This e-mail may contain confidential and/or privileged information
for the sole use of the intended recipient. Any review or distribution
by anyone other than the person for whom it was originally intended is
strictly
prohibited. If you have received this e-mail in error, please contact the
sender and
delete all copies. Opinions, conclusions or other information contained in
this e-mail may not be that of the organization.