Orchestration ignores Use Requirement of Schema attribute

Home Page Forums BizTalk 2004 – BizTalk 2010 Orchestration ignores Use Requirement of Schema attribute

Viewing 1 reply thread
  • Author
    Posts
    • #13060

      For debugging I created two schemas: NameSource and NameDest. Both have three attributes: Fname, Mname, and Lname. I made Mname a \”required\” field on BOTH schemas.

      I test both schema’s without Mname and get errors (as expected). All is well.

      I built a simple transform – and testing resulted in errors again (as expected). All is still well.

      I then built a orchestration that simply receives source… transforms…. sends results.

      I obviously deploy and start the orchestration. When I drop off the test doc, it is processed [u:5b1ab4af0b]WITH NO ERRORS[/u:5b1ab4af0b]. I simply get MName=\”\” in the output XML.

      Why is the orchestration not creating an error on this? It is like the \”Use Requirement\” property is completly ignored in the Orchestration.

      Thanks,
      Michael

      • #13061

        Thank you for the feedback! That really explains a lot.

        Michael

        [quote:8b1db2c75d=\”greg.forsythe\”]The transform shape does not validate either the input or output against the message schema. It just executes the XSLT.

        If you wish to validate a message against its schema you need to use the XmlValidate pipeline component in receive pipeline.[/quote:8b1db2c75d]

    • #13059

      The transform shape does not validate either the input or output against the message schema. It just executes the XSLT.

      If you wish to validate a message against its schema you need to use the XmlValidate pipeline component in receive pipeline.

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