Problems when developing message models

This section outlines some common problems that can arise when working with message sets. It contains advice for dealing with the problems:

Message definition files
Other

Your message definition file will not open

You get a message definition file error in the task list

Your physical format property values have reverted to defaults

You cannot enter text in the Message Definition editor

Objects in your message definition file are not listed in alphabetical order

Error messages appear in the task list after you have imported related XML schema files

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.

A warning appears in the task list because a group contains two different elements with the same XML name in the same namespace

You are having a problem with setting up a message definition file to include a message definition file within another message definition file

You want to make the Properties tab the default in the message definition editor

You get a deprecation error on an imported .mrp file

Your imported message set looks like a simple project

User trace detects an element length error