Creating Service Interfaces from WSDL Files 
The ES Repository provides a wizard to import externally defined WSDL files in the ES Repository and create service interface objects. You use this wizard to reuse existing services by importing them in the ES Repository to create service interface definitions.
In the WSDL definition, each portType reflects a service interface and the messageType reflects the external messages. The wizard maps all the messages in a service interface to the messages that are defined by the external definitions. You can use this wizard to create one or more service interfaces under a given namespace in the ES Repository.
The generated service interfaces will have the same number of operations, request, response, and fault messages as defined by WSDL file. The interface pattern of the generated service interface will be set to Stateless. You can edit this later in the object editor.
Features
Resolving References (WSDL and XSD)
If you select the Import all references option during the Choose file step, the wizard recognizes references from WSDL files to XSD files. The wizard determines the referenced file using the schemaLocation attribute and includes it in the import list. The wizard can only determine the referenced file if the reference is to a file in the local file system (relative).
Messages in the Preview
When creating the import list, the wizard checks whether a service interface can be created for a file in the selected namespace without problems. If there are warnings or errors for the import, you can view these messages in the preview. A message can have the following causes:
The file cannot be imported.
There is already a service interface with the same name in the selected repository namespace of the ES Repository.
There are several files with the same file name (from different directories) in the import list.
The WSDL files to be imported are usually saved in a directory hierarchy. This hierarchy is lost upon import to the ES Repository because all service interfaces are created in one repository namespace. This is the cause of some of the conflicts described above.
The table below provides an overview of messages in the preview and gives an indication of their cause. If the messages can only appear for a particular file type, this is indicated in the table heading.
No. |
Message |
Cause |
|---|---|---|
1 |
The WSDL File <File Name> could not be parsed |
The schema of the WSDL file to be imported is invalid or not supported. |
2 |
The imported WSDL file <File name> has no defined port type |
The WSDL file does not contain a portType definition. |
No. |
Message |
Cause |
1 |
Service interface with the name <Name of definition in ES Repository> already exists |
The ES Repository already contains a service interface with the same name in the namespace in which the service interface for this file is to be created. The wizard would overwrite this service interface during import. Check whether the two service interfaces are identical. If so, you do not need to import the file. If not, you must import the file under another name; otherwise the wizard overwrites the service interface in the ES Repository. |
2 |
Name contains invalid characters: <Invalid character> Only a(A)-z(Z), 0-9, and “_” are permitted |
The name of the service interface contains invalid characters. |
3 |
Name <File Name> is already in the current import list; name <Name of service interface> generated for it |
You have selected two files for import. These files are in different directories and have the same file name. To exclude naming conflicts, the wizard appends a number to the name for the service interface. |
4 |
New name <New operation name> replaces invalid operation name <Old operation name> |
The name of the operation defined in the WSDL file contains invalid characters. The wizard will overwrite this with a new name. |