News Brief

  • Single .jar file
  • Java API & command line exec
  • Structure brought to regex power
  • Complements XSLT




To keep posted about new software releases and features, select one of these newsfeeds
powered_by.png, 1 kB
The end of XML-to-anything asymmetry

An XML document is, by construction, neatly divided into pieces organized as a tree of nodes: element nodes, text nodes, attribute nodes, namespace nodes. When you get a new XML document, the unknowns are names and contents of nodes, but you can trust the cuts, i.e. the tree.  In other words, you see first the structure, and then the contents. These features have forged XSLT which is based on XPath expressions (to select nodes) and a hierarchical application of node processing templates.

An arbitrary text document is just the reverse: you see first a melted content, and then you have to discover the cuts to rebuild the structure. With XSLT, the tree is used to build the processing. With a text file, the processing is used to build the tree. That has forged the ReverseXSL Transformer.

Make XSLT your true any-to-any Mapping Engine (CSV,EDI,Text, Fixed records, Flat Files, ...)
Image May be like many of us, you once thought to use XSLT for a flat-file to XML transformation with the idea that it would be almost as magical as the XML-to-anything developments you formerly achieved. You may have looked for a hidden <xsl:input>(?) method and XSL functions that you haven't used before and that will hopefully provide the solution but... we have to acknowledge that beside framing your entire file with <tag>..myFile..</tag> and using substring() extensively... oups!
Tough operational requirements, screwy formats, and a tight budget molded the reverseXSL Transformer

Air CargoReverseXSL software sprouted in 2007 from the failed attempt to find a straight and flexible structured-messages parser that would be affordable, can be learned quickly, and would not come with dozens of interface screens, gigabyte workstation and server software, plus hundreds of parameters to configure, because communication platforms existed already. Moreover, it had to digest structured airline messages (IATA IMP, AHM, SSIM...) which, if you know them, bear one of the most screwy syntax of the EDI arena.

Learn fast, spend less, and process them all

You have a screwy flat file to import into your application and you are reluctant to endorse one of the solutions presented so far to you... actually, you fear that there could be more parameters to set-up than data elements in your file!

Stop developing non-XML format parsers

Most likely, you had to coordinate three activities:

  1. understand the details of the message syntax at stake and formalize a representation in code
  2. deal with the programming language in itself: edit code, build, unit test, debug, add code to handle exceptions
  3. design and code the logic to deal with optional pieces, repeated blocks, nested structures, conditions, ...

We propose that you drop the last two, and boost your productivity for an even better result!

2016 Art of e.Biz
Powered by [Joomla! is Free Software released under the GNU/GPL License.]