This wiki has undergone a migration to Confluence found Here
<meta name="googlebot" content="noindex">

Difference between revisions of "Implementation FAQ:processing v3 schema with standard tools"

From HL7Wiki
Jump to navigation Jump to search
(Added resolution for .NET 1.1 issues)
 
(2 intermediate revisions by the same user not shown)
Line 1: Line 1:
 
This page documents implementers' experience with tools. Note that the contents of this page do not constitute a recommendation for specific tools by any part of the HL7 organization, the intent is to document experiences and show workarounds if required.
 
This page documents implementers' experience with tools. Note that the contents of this page do not constitute a recommendation for specific tools by any part of the HL7 organization, the intent is to document experiences and show workarounds if required.
  
*There are some known issue with Microsoft .NET v1.1, refer to the following:
+
*Microsoft .NET Framework
** [http://blogs.msdn.com/rruggeri/archive/2006/07/22/674877.aspx Implementing HL7 v3 Using the .NET Framework 1.1]
+
**There are some known issue with Microsoft .NET v1.1, refer to the following: [http://blogs.msdn.com/rruggeri/archive/2006/07/22/674877.aspx Implementing HL7 v3 Using the .NET Framework 1.1]
 +
**The HL7 v3 schemas work right out of the box when using Microsoft.NET Framework 2.0
 
*The Symphonia toolkit (version ??) has a problem with ''minOccurs=0 maxOccurs=0'' and some other strange constructs used in the base datatypes schema. There are a few of those, if removed/tweaked in the schema they can be imported in Symphonia.
 
*The Symphonia toolkit (version ??) has a problem with ''minOccurs=0 maxOccurs=0'' and some other strange constructs used in the base datatypes schema. There are a few of those, if removed/tweaked in the schema they can be imported in Symphonia.
*MSXML (versions prior to v6): messages don't validate, although they're know to be valid. They validate using MSXML v6.
+
*MSXML (versions prior to v6): messages don't validate, although they're known to be valid. They validate using MSXML v6.
 +
*Bizztalk Accelerator
 +
**Issues in v2.0, see [http://blogs.neudesic.com/blogs/enterprise_integration/archive/2007/07/31/13789.aspx this Blog].

Latest revision as of 09:26, 1 August 2007

This page documents implementers' experience with tools. Note that the contents of this page do not constitute a recommendation for specific tools by any part of the HL7 organization, the intent is to document experiences and show workarounds if required.

  • Microsoft .NET Framework
  • The Symphonia toolkit (version ??) has a problem with minOccurs=0 maxOccurs=0 and some other strange constructs used in the base datatypes schema. There are a few of those, if removed/tweaked in the schema they can be imported in Symphonia.
  • MSXML (versions prior to v6): messages don't validate, although they're known to be valid. They validate using MSXML v6.
  • Bizztalk Accelerator