i have got a question regarding handling restrictions in xsd-files. Is there any support while developing a message mapping where unrestricted fields are mapped on fields with restrictions?
Targetfield has got a restriction like this:
Without having a look on xsd-source it's very easy to overlook this information. Not using validation it results in cutting of any letters of a string longer than 70 without giving any information on runtime.
Using validation it should fail on runtime, but is there any tool (mechanism) supporting designtime issues, beside looking up all restrictions in the xsd by myself?