Solution: - Check that a message definition file exists in the workbench for
each of the related XML schema files that you are importing. If the new message
definition files have been created, they will appear in the Resource Navigator.
- Using the Properties Hierarchy in the Message Definition editor, check
that any message definition files that include or import other message definition
files are correctly locating the target 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, while Y is defined
in the notarget namespace. After you import the two files, X is
placed into the location that is 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.