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 new classes and methods to improve translation processing time. 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.3.0 March 19, 2001 Major changes to classes and methods. - Introduced two new classes TemplateTransactionSet and TemplateTables. This is to allow the original TransactionSet to stand alone without it dragging around all the subtemplate objects that are used by segments, composites and dataelements. Also it speeds up loading transaction sets objects by using one TemplateTranasctionSet for many TransactionSet objects. Applications acting as Servers and applications parsing multiple transactions sets in one envelope will notice improvement in processing time. Independent Beta Test EDI X12 documents to XML. File Size 2.2.0 Release 2.3.0 Release 360kb 1039 seconds 159 seconds 18kb 91 seconds 7 seconds 267kb 374 seconds 40 seconds - Added logic to transactionSetFactory class to remember TemplateTransactionSets it has loaded. This will reduce load time when a transaction set is reloaded by reducing file i/o. See above. - EXTENDED ADDITION ONLY added ability to define data element default values inside of the XML rules file by introducing a new subelement of dataElement named default. The default value has one attribute "from". Using the from attribute and the #PCDATA contents data elements can be assigned default values by using the data elements useDefault method. 1.if from is equal to "constant" then the PCDATA field is used as the default value. So if <default from="constant">setbyconstant</default> was specified then when the useDefault method is called the data elements field would be set to setbyconstant. 2.if from is equal to "property" then the PCDATA field points to a field in the oboe .properties file. So if <default from="property">property840</default> was specified the application would look in the oboe.properties file for the property property840 and set the dataelements value to the value associated with the property. 3.if from is equal to "method" the PCDATA field defines a static method in a class to pull the default value. For example: <default from="method">com.mycompany.edi.myClass#myMethod</default> Informs the package to use the static method myMethod in class com.mycompany.edi.myClass which has been defined to return a String. An example of the class and method definitions as follows: package com.mycompany.edi; public Class myClass { public static String myMethod() { returns "something"; } } Minor changes to classes and methods. - Moved the xmlDirectoryPath variable to the util.Util class and made it static. - Added two new methods to util.Util setXMLDirectory and getXMLDirectory. --- 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/
