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


This release includes an event driven parser and handler classes.  These new classes 
were introduced to allow parsing of EDI objects containing a large number of 
transaction sets.

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 engine is available with an Open Source license.

Release 2.2.0 February 14, 2001
       Major changes to classes and methods.
          Created new abstract parser class DocumentParser and two distinct classes 
X12DocumentParser and EDIFactDocuementParser.
          It turns out that the container class Envelope had some size limitations. 
While running on a large mainframe this size issues was
          never found, but it became apparent when running in other environments. The 
DocumentParser class is an event driven class, much
          like the SAX XML parser. When the parser finds a particular EDI object it 
reports its findings to all registered DocumentHandler
          objects.
          Objects reported on and when:
          Start of Envelope
               at creation
          End of Envelope
               when completed
          Start of FunctionalGroup
               when a FunctionalGroup Header Segment is found
          End of FunctionalGroup
               after a FunctionalGroup Trailer Segment is parsed
          Start of TransactionSet
               when a TS header segment is found
          End of TransactionSet
               after a TS trailer segment is parsed.
          Start of Segment
               ONLY ENVELOPE and FUNCTIONAL GROUP SEGMENTS are reported.
               when a Segment is created.
          End of Segment
               ONLY ENVELOPE and FUNCTIONAL GROUP SEGMENTS are reported.
               after the Segment has been parsed
          Created a interface DocumentHandler and two distinct classes 
X12DocumentHandler and EDIFactDocumentHandler.
          These are the classes that are used to register with the DocumentParsers. 
The DocumentParser will notify the handler classes at
          certain times for particular EDI objects.
          The x12.Parser and EDIFact.parser classes are now deprecated and will be 
remove from some future release. x12.Parser is
          replaced by x12.X12DocumentHandler. EDIFact.Parser is replaced by 
EDIFact.EDIFactDocumentHandler.
       Minor changes and bug fixes
          Segment class getSegmentCount did not include array of segments in its logic.
          When OBOEExceptions are thrown by data element objects, exception message 
now includes data element id.


---
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/

Reply via email to