I was recently asked to talk at the European eInvoicing and eBilling conference about better ways to integrate the transfer of e Invoicing and e billing into existing applications and security solutions. By the way, it was held in Munich and, if you go, definitely check out the surfing at the south end of the Englischer Garten.
XSLT 2.0 and to some extent 1.0 are powerful languages when it comes to transforming documents and even for performing some tasks. But, as is often the case, to do something odd or unusual can often be impenetrable or just plain difficult. One of the advantages of using Intel® SOA Expressway is that most of the extension functions we have written to make configuration easier for BPEL based workflow are also available to the XSLT developer.
Altova is well known for it's flagship product XMLSpy - as anyone who has worked extensively with XML data can tell you. However, they have an entire suite of product offerings, one of which is MapForce. As described on it's website:
A typical Healthcare Information Exchange (HIE) accepts data from an array of disparate sources. Often the data it accepts is semantically and syntactically altered by a providing system to satisfy interfacing requirements. However, there are also cases where data from different sources need to be properly merged before reaching the HIE's interface.
For the past 7 weeks I worked on my first Proof-Of-Concept (POC) for a financial system corporation. The initial scope of the work revolved around using SOA Expressway primarily as rapid & high performance secure integration product.
December 2012: This WhatIf project has been retired, but will remain here for reference.
XSLT 2.0: Regular expressions
One of the weaknesses in XSLT 1.0 was the very simple set of string manipulation features. In comparison to many popular programming languages, the string functions lacked one very powerful feature, regular expressions. Intel SOA Expressway actually offers this functionality with extension functions for our customer base. In XSLT 2.0, the XSLT working group plugged this hole for everyone in a couple of ways that we’ll look at in this post.