Document type does not match any of the given schemas.

Home Page › Forums › BizTalk 2004 – BizTalk 2010 › Document type does not match any of the given schemas.

Viewing 1 reply thread
  • Author
    Posts
    • July 21, 2006 at 2:50 PM #14046
      community-content

        Looks like now I’m facing this issue:

        http://geekswithblogs.net/dmillard/archive/2004/12/10/17250.aspx

        This regards mapping TO an envelope schema.
        We receive data from a vendor, and want to \”scrub\” it and write to an envelope schema, then debatch it. The debatch is working, and the XSLT by itself to map to the envelope schema works. It just doesn’t work \”automatically\” on the receive port.

        I just wondered if any new solutions have come up.
        I hate to use an orchestration just to get around this error.

        Here’s the error:

        The Messaging Engine failed while executing the inbound map for the message coming from source URL:\”c:\\CompassionServices\\File Drops\\ISADailyBatchIn\\*.xml\” with the Message Type \”ci1xmltest\”. Details:\”Document type \”http://schemas.compassion.com/constituent/batch/cprinfo/2006-06-01#CPRInfo\” does not match any of the given schemas.

        Also see:
        http://www.webservertalk.com/archive178-2004-8-338739.html

        http://hugorodgerbrown.blogspot.com/2004/12/envelopes-maps-and-pipelines.html

        Thanks in advance,
        Neal

        • July 24, 2006 at 6:00 PM #14047
          community-content

            I did get it working by creating a simple orch that does a receive/map/send.

            [quote:5dda000740]I’m just curious. What’s the reason you are mapping to an Envelope Schema? [/quote:5dda000740]
            We receive a file in a rather odd XML format from a vendor.
            So the first XSLT turns it into the data we want, but still in one big batch.
            Our batch schema is basically a wrapper for one of our existing schemas.

            Then we use the envelope schema to debatch it (no orch).

            • July 26, 2006 at 7:01 PM #14048
              community-content

                I thought of that, but needed to get something working fast. Wouldn’t the problem be that you can have two schemas deployed with the same root element and same namespace? If the root or namespace were different, then you have to map it again, or do some kind of string/replace in an orchestration, which again defeats the purpose of doing it directly in the file receive port.

                • July 26, 2006 at 1:33 AM #14049
                  community-content

                    I’m kinda curious… has anyone tried defining the envelope schema twice? one marked as an envelope schema and one as a regular document schema; and just doing the map against the document-one and doing the debatching against the envelope one. A pita, but it might work….

                    • July 26, 2006 at 7:08 PM #14050
                      community-content

                        Well, for pipelines, you’d need to select the right one as the document/envelope schema on the XmlAssembler/XmlDisassembler components, but that would pretty much be it. I must admit I haven’t tested what would happen with a map in an orchestration, though, but I’d assume it should work (since the message in the orch. itself is strongly typed).

              • July 24, 2006 at 5:33 AM #14045
                community-content

                  I’m just curious. What’s the reason you are mapping to an Envelope Schema?
                  I’m wondering since the map happens after the pipeline so I’m not sure that the Envelope is being used for. I’m guessing used on the outbound?

                  What about mapping inside an Orchestration?

              • Author
                Posts
              Viewing 1 reply thread
              • The forum ‘BizTalk 2004 – BizTalk 2010’ is closed to new topics and replies.