Enhance the New Message Model wizard to import WSDL files from URL using same function as local WSDL files

When using the "New Message Model" wizard you have the option to create the model from an existing WSDL file. The behavior of the wizard is different if the WSDL file is accessed from the workspace or from a URL.

When accessed from the workspace you have an opportunity to specify which folder the generated WSDL and XSD files are written to. The names of the file that are generated are also generated to include the name of the WSDL file as the first portion of the file name. For example, if a WSDL file named DistributorService.wsdl is imported from the local workspace into a folder named Distributor a set of files will be created in a folder named Distributor with the names of DistributorService.wsdl, DistributorService.xsd, DistributorService_InlineSchema1.xsd, DistributorService_xsd0.xsd and DistributorService_xsd1.xsd.

When accessed from a URL the generated files are arbitrarily written to a folder named RemoteFiles. There is no control over the folder name. The file names that are generated are also handled differently. In this case the XML schema documents that are generated from INCLUDE and IMPORT directives are always named with an "xsd_" prefix rather than a prefix of the WSDL file name. For example, importing a WSDL file from a URL that references a WSDL file name of MDM will generate the following files in the RemoteFiles folder: MDM.wsdl, MDM.xsd, MDM_InlineSchema1.xsd, xsd_xsd0.xsd and xsd_xsd1.xsd.

The use of the "xsd_" prefix for all URL referenced files causes problems when you attempt to create a Message Model from more than 1 URL based web service into a single Library. Each additional Message Model that you create will overwrite the existing "xsd_" prefixed schema documents, which corrupts the existing Message Models.

Using a separate Library to hold Message Models will alleviate the problem in the Toolkit, but does not fully resolve the issue. If more than 1 Message Model that is built from a URL based WSDL is deployed to the same Execution Group there will still be a clash due to the sharing of the RemoteFiles folder in the runtime.

The "New Message Model" wizard needs to be modified to allow URL based WSDL's to store their generated files in separate folders, the same as workspace based WSDL files.