From: Tripp, B. <Bry...@uh...> - 2003-11-05 21:53:43
|
HAPI 0.4 is now available for download ... https://sourceforge.net/project/showfiles.php?group_id=38899 Thanks for your patience. Please let me know if you encounter any problems. Bryan Changes since 0.4 beta: change build to compile core with debug line numbers add wildcards for MessageTypeRouter fix missing segment location on HL7Exception during parse handle Varies in Terser setter (check type and switch to GenericComposite if comp > 1) allow unexpected components on composites update PipeParser to allow unexpected components allow unexpected field repetitions add hook for testing table values in profiles (profile, table / codeSystem) per Lloyd's suggestion handle nnnn as wildcards in codes lookup table for events that don't map directly to message structures fix new DB errors noted on Frank Oemig's web page v2.2 PN: getFamiliyName should be getFamilyName add getXReps to generated code for repeating structures add HapiLog to docs and core source log4j config in release incorporate Alexei's GenericHL7Message fix update DeepCopy to allow extra components update TreePanel to show extra components fix wildcard handling in AbstractCodeStore to treat wildcard-containing codes as special cases, handle comma delimiter fix docs in HL7Service re registration use HAPI_HOME property for custom_packages, configuration, id_file, etc. add libs to distribution with Class-Path entry in manifest (use like -classpath %HAPI_HOME%\hapi.jar) add copyright & license with libs remove commented code from PipeParser change MSH-9 to CM_MSG in v2.1 change message in DefaultValidator: Value 'x' doesnt' equal constant value of 'y' remove Status references and deprecate in DefaultValidator, skip validation of X (not used) elements 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. |