A new release of OBOE Open Business Objects for EDI has been posted on the American Coders web site. For more information visit http://www.OpenBusinessObjects.com OBOE translates between several Electronic Data Interchange (EDI) document formats and EDI/XML files. The package is targeted at legacy EDI users who want to integrate their systems with the Internet quickly and easily using standards based technology. The OBOE package comes with an Open Source license. Release 2.1.0 January 15, 2001 Major changes to classes and methods. ValidXMLParser can handle both XML envelopes as defined in envelope.dtd and transactionsets as defined in transactionset.dtd Created ISegmentContainer which defines getter/setter methods for the segments that the envelope contain. This work required for the valid XML parser. Envelope, X12Envelope and EDIFactEnvelope implement ISegmentContainer FunctionalGroup, X12FunctionalGroup and EDIFactFunctionalGroup implement ISegmentContainer SegmentContainer abstract class implements ISegmentContainer Moved addFunctionalGroup method in X12Envelope and EDIFactEnvelope up to abstract class Envelope. DateDE will truncate (without warning) century if max length is set to 6. DateDE getFormattedText for XML requests will return date in YYMMDD or YYYYMMDD style. This is to make parsing the text easier. EDIXMLParser class rewritten to look more like ValidXMLParser. Now only one constructor. Constructor takes no arguments. Old constructors changed to parse(... method. Old parseString, parseFile... removed See EDIXMLParser documentation for more information Minor changes and bug fixes Envelope getFormattedText didn't call EDIFAct Service String Advice segment's getFormattedText For getFormattedText methods using either XML format requests the value field is first passed to Util.normalize method to (obviously) normalize the data. Not called in the numeric and data/time classes, will this data ever be abnormal? XML header output was still in the transactionset getFormattedText XML request sections. Now in envelope getFormattedText methods. CompositeDE was adding group delimiter when not necessary Removed checking minimum length in NumericDE set method. EDIXMLParser not handling comments Changes to DTD and XML files The ValidXMLEDIParser class now uses the envelope.dtd file. Meaning that it parses an XML file that contains the envelope and functional group objects introduced in release 2.0.0. Note that the class can still parse an XML containing a stand-alone transaction sans envelope and functional group objects. Valid XML envelope data requires a format field specifying either X12 or EDIFact. --- Joe McVerry, President and Chief Technical Officer American Coders Ltd. POBox 97462 Raleigh, NC 27624 USA 919.846.2014 AOL-IM: USACoder http://www.americancoders.com Home Of OBOE - Open Business Objects for EDI xBaseJ - xBase Database Engine For Java ======================================================================= To contact the list owner: mailto:[EMAIL PROTECTED] Archives at http://www.mail-archive.com/edi-l%40listserv.ucop.edu/
