This section outlines some common problems that can arise when working with message sets. It contains advice for dealing with the problems:
Message Definition File '<mxsd name>' has been corrupted. The error is as follows:
One common scenario is where you have two XML schema files X and Y, which both exist in the same directory in the file system but where X, which includes Y, is defined with a real target namespace, whilst Y is defined in the notarget namespace. After you import the two files, X is placed into the location determined by its namespace, but Y is placed into the default namespace location used for files defined in the notarget namespace. This causes the link between the two files to break, and you must modify X so that it correctly includes Y in its new relative location. See Linking from one message definition file to another for further details.
This warning is sometimes only partially displayed. If this is the case, enlarge the properties page size.
@deprecation - Complex Elements are deprecatedor:
@deprecation - Embedded Simple Types are deprecated
ParserException BIP5195E: Invalid element length
Related concepts
Message sets
Message definition files
Simple types
Message model objects
Related tasks
Creating a message set
Working with a message definition file
Dealing with problems
Working with message model objects
Configuring physical properties
Migrating a message set
Related reference
Message set projects and files
Message Definition editor
Message set migration notes
Notices |
Trademarks |
Downloads |
Library |
Support |
Feedback
![]() ![]() |
au16520_ |