- This topic has 2 replies, 1 voice, and was last updated 9 years, 5 months ago by
.
-
Posts
-
-
Hi everyone.
We would like to use Biztalk 04 to realize communication with one of our customers. The customer uses schemas provided by the Open Applications Group. However, the OAGIS schemas (7.2.1.) don’t work correctly in our Biztalk Server (003_process_po, 057_change_po, 161_show_shipment). We tried the supplied .xsd-files. Converted and tried the supplied .dtd- and the sample .xml-files.
Manually editing the generated files resolved some major errors. So validating the schemas works correctly, but the generation of sample .xml-files and validating these against the Schema-files creates serveral errors as validating the supplied .xml-files do.The point is that we can’t use the Schemas in the BT-Server and/or can’t validate or check any xml-files
against these schemas.Does anyone know these kind of errors and/or has a solution or workaround?
Any help would be much appreciated.Thanks in advance.
Peter -
-
I have had the misfortune of using the OAGIS 7.2 schemas on an integration project. I had exactly the same problems as yourself.
In the end I created my own schema from scratch that only contained the fields I needed. The Xml message would validate against both the official and my custom schema. You must include all required fields but you can exclude some of the ugly bits like recursive lines.
I used the 171_process_invoice, in which an invoice line record can contain an invoice line record.It also gets really ugly when you need to map one of these messages, especially if you have a lot of date fields like this
[code:1:f414ea9491]<DATETIME qualifier=\"CREATION\">
<YEAR>1996</YEAR>
<MONTH>06</MONTH>
<DAY>30</DAY>
<HOUR>23</HOUR>
<MINUTE>59</MINUTE>
<SECOND>59</SECOND>
<SUBSECOND>0000</SUBSECOND>
<TIMEZONE>+0100</TIMEZONE>
</DATETIME>[/code:1:f414ea9491]I ended up using a custom Xslt and made good use of <xsl:template>
-
- The forum ‘BizTalk 2004 – BizTalk 2010’ is closed to new topics and replies.