Paul's Petrov Whiteboard

[BizTalk, Enterprise Application Integration, Business Process Automation, SOA, .NET]

  Home  |   Contact  |   Syndication    |   Login
  67 Posts | 1 Stories | 133 Comments | 30 Trackbacks

News

Archives

Post Categories

Image Galleries

BizTalk

Other

XML

Microsoft BizTalk Accelerator for HL7 comes with multiple versions of the HL7 implementation. One of the typical integration tasks is to receive one format and transmit another. For example, system A works HL7 v2.4 messages, system B with v2.3, and system C with v2.2. The system A is exchanging messages with B and C. The logical solution is to create schemas in separate namespaces for each system and assign maps on send ports. Schematic diagram of the messaging solution is shown below: Nothing is...
  • Share This Post:
  • Share on Twitter
  • Share on Facebook
  • Share on Technorati

Repeating sequence groups can often be seen in real life XML documents. It happens when certain sequence of elements repeats in the instance document. Here’s fairly abstract example of schema definition that contains sequence group: <xs:schemaxmlns:b="http:... xmlns:xs="http://www.w3.org... xmlns="NS-Schema1" targetNamespace="NS-Schema1" > <xs:elementname="Repeati... <xs:complexType> <xs:sequencemaxOccurs="1...
  • Share This Post:
  • Share on Twitter
  • Share on Facebook
  • Share on Technorati

I notice often developers don't pay much attention to the XPath queries they use. And then some complaining about XML performance. Of course, XML means overhead but we're here not to make it worse. For example, such convenient descendant-or-self axis specifier (AKA “//”) can be frequently abused without realizing how much harm it can bring to high volume XML processing applicaitons. Say we have an XML message with simple structure like this: <Root> <Inventory1> <item0>0</item0>...
  • Share This Post:
  • Share on Twitter
  • Share on Facebook
  • Share on Technorati