|
EDI Integration using Jitterbit |
|
Saturday, 16 August 2008 |
|
Jitterbit is the leading open source integration platform. For its supported customers, Jitterbit offers EDI integration based on EDIReader and EDIWriter. This feature allows you to use Jitterbit's XML graphical mapping tools to define transformations between EDI transactions and your internal formats. Go to http://www.jitterbit.com for more information. |
|
|
Enhanced support for HIPAA transactions |
|
Wednesday, 30 July 2008 |
|
A HIPAA module is now available with the commercial version of EDIReader in support of the primary X12 transactions adopted by HIPAA: 270, 271, 275, 276, 277, 278, 820, 834, 835, 837. This module includes the necessary plugins and a special adapter that allow EDIReader to produce an XML expression of a HIPAA EDI transaction that reflects the detailed internal looping structure of the transaction. For example, the output XML for a 270 Eligibility Inquiry shows the 2000A, 2000B, and 2000C loops based on the hierarchical relationships defined by the HL segments within the transaction.
|
|
|
Recoverable syntax exceptions |
|
Wednesday, 25 June 2008 |
|
A new feature in the commercial version of EDIReader allows the user to provide a Java callback method for certain EDI errors from which EDIReader is able to recover. For example, EDIReader detects that the control number appearing in the segment marking the end of an interchange matches the control number that appears at the beginning of the interchange. By default, EDIReader throws an EDISyntaxException for such invalid EDI constructs, but a user-provided callback may now handle this and other recoverable exceptions and allow parsing to continue.
|
|
|
Generating EDIFACT CONTRL Messages |
|
Thursday, 08 February 2007 |
|
EDIReader now supports the automatic generation of EDIFACT CONTRL messages as an optional by-product of parsing EDIFACT interchanges, similar to its support for X12 997s. All of the syntax and version choices, along with the addressing details, are inferred from the original message. All that is necessary is to provide the EDI parser with a java.io.Writer object to be used for the generated output. |
|
|
Using EDIReader with J2SE 5.0 XPath Evaluation |
|
Saturday, 03 February 2007 |
|
The XPath Evaluation API, new in Java 2 SE 5.0, may be used to query EDI content with EDIReader. This provides an alternative to XSLT or JDom/Jaxen approaches which are still available. To use the XPath Evaluation API, you use EDIReader as a SAX parser to build a W3C DOM by means of a Transformer. XPath queries can then be performed against the EDI data as illustrated in the program portion shown below.
import com.berryworks.edireader.EDIReaderFactory;
import ...
public class QueryEDIwithXPath {
InputSource inputSource =
new InputSource( new FileReader( "edi.dat" )); String query = "/ediroot/interchange/group/transaction/@DocType";
public String query() throws Exception {
XMLReader ediReader =
EDIReaderFactory.createEDIReader( inputSource );
DOMResult dom = new DOMResult();
Transformer transformer = TransformerFactory.newInstance().newTransformer();
transformer.transform( new SAXSource( ediReader, inputSource), dom );
return XPathFactory.newInstance().newXPath(). evaluate( query, dom.getNode() );
}
}
|
|
|
|