XML on Marko Apfel

Visual Studio: Find in files with *.xml wildcard does not find all occurrences

Tue, 17 Nov 2009 04:51:00 +0100

During a refactoring we searched for full type names in our IoC-config files. The filter was setted to *.xml and Visual Studio does not found all occurrences of the search string in these xml-files.

Sandcastle Help File Builder: Content Editor opens without functionality

Thu, 16 Apr 2009 10:52:00 +0200

If the content editor of SHFB opens without any functionality then the configuration file is corrupt.

This is repairable through deleting the config-files under C:\Documents and Settings\[YOUR\_USER\_ID]\Local Settings\Application Data\Eric\_Woodruff\...

Sometimes an error occurred during opening content editor next time. In this case you must study the message. Often you have created a not XML-wellformed content file. Open your last used files with an other XML-editor and look for the place which is described in the message. After fixing the prob you must close SHFB, delete the config-file again and reopen your SHFB-project.

Mapping -Elements in BizTalk-Orchestrations

Wed, 14 Feb 2007 16:21:00 +0100

Mapping <Any>-Elements in a BizTalk-Map is not possible. You can not draw a direct connect from or to <Any>-Elements.

Some sources in the web describe the possibility to use a scripting-functoid with a special XSLT to do that, other sources recommend to write a special .NET-component to insert the wished tree under the <Any>-Element.

Möglichkeiten des Message-Handlings in Orchestrations

Wed, 07 Feb 2007 14:30:00 +0100

Für das Handling von Messages in Orchstrations gibt es verschiedene Möglichkeiten.

Eine gute Beschreibung ist von Matt Meleski “Constructing BizTalk 2004 XML Messages (In an Orchestration) - Choices”

Nebenbei haben sich bei mir noch folgende Varianten angesammelt

BizTalk und NameSpaces

Thu, 23 Mar 2006 23:45:00 +0100

Unterschiedliche Namespaces zwischen Schemas und Instanzen führen immer wieder zu kryptischen Fehlermeldungen.

Die Erfahrung zeigt, dass es einige besonders tückische Stellen gibt, die man sofort verifizieren sollte.

Typische Fehlermeldungen

Namespace-Referenzierung in der Instanz passt nicht zur deklarierten im Schema

There was a failure executing the receive pipeline: "Microsoft.BizTalk.DefaultPipelines.XMLReceive, Microsoft.BizTalk.DefaultPipelines, Version=3.0.1.0, Culture=neutral, PublicKeyToken=31bf3856ad364e35"
Source: "XML disassembler"
Receive Port: "RpIn"
URI: "C:File_InMiniTest*.xml"
Reason: Finding document specification by message type "de.MeineFirma.EAI.Schema.FalscherTyp#MyEntity" failed.
Verify that the schema is deployed properly.

Komplette Namespace-Referenzierung in der Instanz vergessen

There was a failure executing the receive pipeline: "Microsoft.BizTalk.DefaultPipelines.XMLReceive, Microsoft.BizTalk.DefaultPipelines, Version=3.0.1.0, Culture=neutral, PublicKeyToken=31bf3856ad364e35"
Source: "XML disassembler"
Receive Port: "RpIn" URI: "C:File_InMiniTest*.xml"
Reason: Finding document specification by message type "MyEntity" failed. Verify that the schema is deployed properly.

Receive-Pipeline falsch konfiguriert, z.B. auf PassThruReceive anstatt auf XMLReceive

The Messaging engine failed to process a message submitted by adapter:FILE Source
URL:C:File_InMiniTest*.xml.
Details:The published message could not be routed because no subscribers were found.
This error occurs if the subscribed orchestration schedule or send port has not been started, 
or if some of the message properties necessary for subscription evaluation have not been promoted.

Folgende Einstellungen sollten immer passen

Schema an sich (Auswahl der XSD-Datei)

Namespace: de.MeineFirma.EAI.Schema
Type Name: MeinTyp

macht zusammen für den Full Qualified Name ein de.MeineFirma.EAI.Schema.MeinTyp

BizTalk Server 2006 Error: Loading document specification XYZ from assembly XYZ failed.

Mon, 20 Mar 2006 02:00:00 +0100

Obwohl die Assemblies mit den Schemas im GAC und deployed sind, kommt es beim Aufpicken einer Schemainstanz zu 2 Fehlereinträgen im Eventlog und die Message wird supended.

Fehler

Event Id: 5753
A message received by adapter "FILE" on receive location "XML" with URI "C:File_InORDERS01*.xml" is suspended. 
Error details:
There was a failure executing the receive pipeline:
"Microsoft.BizTalk.DefaultPipelines.XMLReceive, Microsoft.BizTalk.DefaultPipelines, Version=3.0.1.0, Culture=neutral, PublicKeyToken=31bf3856ad364e35"
Source: "XML disassembler"
Receive Port: "RpORDERS01"
URI: "C:File_InORDERS01*.xml"
Reason: Loading document specification from assembly failed. Verify that the schema for this document specification is deployed and placed in the Global Assembly Cache.

und

Communication BizTalk to SAP via IDoc

Thu, 09 Mar 2006 16:26:00 +0100

Now with some little corrections the IDoc goes to SAP. Both Flatfile and XML IDocs can be pickuped and delivered to SAP.

First at all you need a Send Pipeline (e.g. spORDERS01) with a Flat File Assembler to transform a XML- to a Flatfile-IDoc. As the Document Schema you specify the imported schema from SAP (e.g. ORDERS01). This Send Pipeline you must choose as the Send Pipeline in the configurationdialog from the Send Port for the SAP-system. It is a good idea to put all pipelines in a own assembly. It prevents the loosing of this setting during a new build of the intrinsic project.