|
|
This description is for version 2.xx of the import tool.
The current version is 2.03. Change history for version 2.xx.
One basic task that must be performed in TransacXML is the modeling of XML documents in the Plex model. Previously this has been a manual process, where you translate the structure of an XML document to specific Plex objects and structures.
However, for complex schemas this can be a time-consuming and a potentially quite error-prone process. To assist in this process we have developed a tool that can import W3C XML schema definitions into Plex.
The import tool can handle:
The import tool uses the information in the files to create a Plex XML Import file. This file can be imported into Plex using the XML import functionality.
The .NET 2.0 framework must be installed on the PC where you want to run the tool.
You can check whether you have the framework installed by going to Control Panel → Add or Remove Programs → Change or Remove Programs:
Another way to check it, is simply to install the tool and try to execute it - if you get an error stating that the application failed to initialize properly, it is because the framework is not installed.
Download the framework at http://www.microsoft.com/download/en/details.aspx?displaylang=en&id=19
The tool is delivered as an install shield file: TransacXMLImporters.exe.
Run this file to install the import tool.
After installing the tool, you can access it from the Start menu.
If you want to uninstall the tool, go to Control Panel → Add or Remove Programs → Change or Remove Programs, select the entry for TransacXML Import Tool and press Remove.
The tool currently performs the actions that we have found to be the most necessary to improve the creation of the modeling in Plex - and nothing else.
Please note the limitations described for the WSDL and the Schema import:
As both the WSDL and the W3C schema standard are quite complex, we can't guarantee that all valid schema or wsdl files can be imported. Some structures simply can't be handled by Plex or by the TransacXML modeling and in some cases, there will surely be some structures that we haven't been aware of when creating the import tool.
Should you encounter problems when using the tool, you are of course also welcome to contact Websydian Support.
It will be a great help if you provide us with the schema/wsdl file that has caused the problem and information about any error messages etc. that has been shown - and please specify the version of the import tool you are using.
You are encouraged to send improvement requests to Websydian Support. Of course we can't guarantee that the requested changes/improvements will be made, but it is important for any further development of the tool that we get as much feedback as possible.
This version handles the following errors:
An error occurred when importing a WSDL containing a RPC/literal message, where a part referred an element instead of a type in the schema.
A special situation where a RPC/literal message erroneously was imported with encoding information for the parts.
An error occurred when importing RPC/encoded services due to an error in the reference to the soap-encoding schema and the schema for describing W3C schemas.
This version adds the following functionality:
In the settings.xml file, you can add two additional elements: "scope" and "longnamemethod". These settings allow you to specify a scoping entity for the imported XMLElement structure in Plex and allows you to specify two new ways to assign literals for the long name source codes.
Informational messages from the schema import can be saved to a text file.
This version handles the following error:
A service that contained both a SOAP 1.1 and a SOAP 1.2 port was not be resolved correctly if the SOAP 1.2 port element was placed before the SOAP 1.1 port element in the service element.
Online documentation - Websydian v6.1