RE: [HAPI-devel] hi, patch to load a default class when no messag e-class mapping is found

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

Hey, not bad!  We should definitely include this.  I want to try to finish
the handling of unexpected segments this week.  Once that's done this could
be made even simpler ... just use a constant DefaultHL7Message and any
segments that show up will be handled automatically.  Does that fit with
what you had in mind Alexei?  
 
Also, for times when you just want a few fields from a message (e.g. for
routing, acknowledging every message in a stream), Dan is working on a
preparser that just extracts the specific fields you ask for and puts them
in a Properties object.  This is meant to be really fast, so we can start to
handle higher volumes.  Should be ready today, he says.  
 
Bryan 

-----Original Message-----
From: alexei guevara [mailto:ale...@ho...]
Sent: April 14, 2003 11:39 AM
To: hl7...@li...
Subject: [HAPI-devel] hi, patch to load a default class when no
message-class mapping is found


Hi 
 
I was in need of making hapi parse any kind of HL7 messages (including
custom ones, not kown at deployment time). To accomplish such behavior I've
changed the Parser.findMessageClass, check the javadocs of that method
(included in the attached zip file) for details.
 
alex6
PS: a very simple test case is included in the zip file as well.



MailFiler <http://www.mailfiler.com>  [AG-7IS2CX]



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.