Importing WSDL and XSD Files

Use

You can import service interface definitions or XSD documents in your application model and compose a new service or simplify the imported service interface. Your application model does not directly use the WSDL and XSD files that you import and are contained in your project. The documents are first imported into the Enterprise Service Modeling (ESM) repository, which saves the imported data in its own proprietary format in the rep/wsdl folder of your project. The repository is seamlessly integrated in your project.

When you import a WSDL document into your project, a conflict may occur if an interface defined in the WSDL had been already imported in ESM by another document and the two definitions are different. The difference may be in the number of operations, in one or more operations' input, output or fault message definitions, and so on. Such two documents cannot exist in the repository at the same time. Note that the conflicting interface may be defined not in the currently imported document, but in a document referenced by it because when a document is imported, all referenced (imported and included) documents are also imported.

If such a conflict occurs, a dialog prompts you to choose whether to continue with the import or to cancel it. If the interface you are trying to import is a newer version of the existing one, you may continue with the import. The import thus acts as a reimport of an existing document, so as much information as possible will be preserved from the old interface definition. However, all documents that refer to the old interface will be automatically deleted from the ESM repository. The WSDL files will not be deleted from the file system unless you select the Delete documents from the file system checkbox. Note that the WSDL files are visible in your project, but have a warning marker.

If you need to use both definitions of this interface, choose No and import the current WSDL in another project. Note that the WSDL appears in your project, but with an error marker.

When you import or reimport an XSD file in the repository, it is possible that one and the same entity (with the same qualified name) has a different definition in the document that you are trying to import, compared to the definition already existing in the repository and defined by other documents. Such different definitions of the same entity are not allowed in the repository because of the qualified name uniqueness concept. If such a conflict occurs, in the dialog that appears you can choose one of the following options:

• Choose the Update Files pushbutton - the entity definition in the document you are trying to import overrides the old entity definition, both in the repository and in the files of the already imported documents. The new document will be imported. Use this option with caution because it might have a severe impact on runtime. Choose this option only if you are sure that all existing services containing this entity have changed and use the new entity definition. If you are not sure, get the latest versions of these documents, reimport them, and if you still receive this conflict, reject the import.

• Choose the Reject pushbutton - the document that you are trying to import is not imported in the repository. If you still want to use this document, you must import it into another project.

You can see all the documents that define a conflicting entity by choosing the Show/Hide Affected Schemas pushbutton, located in the top-right corner of the compare dialog.

If you want to use a modified service interface or XSD file, you can reimport it in your project. For more information, see Reimporting Modified WSDL and XSD Files .

Procedure

More Information

For more information about the search capabilities you can use in the Search Console, see Browsing Services in Search Console .

For more information about import and reimport preferences, see Configuring Import and Reimport Preferences .