Web Services Migration (Magic xpi 4.13)
The Web Services implementation is changed since Magic xpi 4.12. For the existing projects, developed prior to Magic xpi 4.12, the Web Services Client resource and step will be migrated/upgraded once you open the project in Magic xpi 4.12. Appropriate error messages, warning messages through checker process will be provided, in case steps and or resources could not be migrated/upgraded properly or when the Operation Out parameter at the time of Step configuration is not set to Blob type.
For projects created prior to Magic xpi 4.12, for Document type WSDL, a Data Mapper step was required before the Web Services Client step to provide the required mappings to be sent in the Web Service call. This Data Mapper step had to be configured with the blob parameter and then set in the Web Services step.
This same behaviour is retained for the migrated projects as well. The migrated projects will also get the Data Mapper step with one blob parameter. To do any changes to the mapping in the migrated projects, the user will still have to use the Data Mapper step.
For newly created projects, with new Web Services Client resource and step, this additional Data Mapper step is not required and the user can do the mappings on the Web Services step itself. This can be done by double clicking on the Web Services step to open the Data Mapper.
After migration, the Migrated Resource field on the Web Services Client resource will be set to Yes to distinguish it from the newly created resource.
|
|
Before Migration, set the correct path of the WSDL in Web Services Client resource otherwise, migration may fail.
|
For the migrated or upgraded projects, the migration log for the Web Services consumer can be seen under the relevant section in the MagicXpi.Log file.
Refactoring Limitations for Web Services Steps Migrated from pre-Magic xpi 4.12 Version
Web Services Troubleshooting
