Data Mapping for 3.1.x to 3.4 Migration

This section explains the steps for migrating General Interface 3.1.x projects that use data mapping to General Interface 3.2 and 3.3.

For data mapping, there are two steps to updating your project:

1. Update rules files.
2. Modify the loadResource() method call in the JavaScript code.

Updating Rules Files

The format of data mapping rules files has changed in General Interface releases after 3.1.x. Mapping rules files from 3.1.x will not run in 3.3. General Interface Builder includes logic for converting 3.1.x rules files to 3.3. Simply open each 3.1.x rules file in the XML Mapping Utility (formerly SOAP Mapping Utility) in General Interface Builder 3.3 and save it. The 3.1.x rules file is automatically updated to the 3.3 format. To open the XML Mapping Utility, choose Tools > Communication > XML Mapping Utility.

Modifying the loadResource() Method Call

The JavaScript code generated by the XML Mapping Utility has changed due to a signature change in the loadResource() method (jsx3.app.Server). The rules file ID is now passed as a parameter instead of the URL. Update all legacy code generated by the XML Mapping Utility as shown in the New Code for 3.3, below.

Code for 3.1.x

var objService = new jsx3.net.Service(Rules_File_URL, Operation_Name);
objService.setNamespace(namespace);

New Code for 3.3

var objService = Server_Name.loadResource(Project_Resource_File_Id);
objService.setOperation(Operation_Name);

setOutboundStubURL() and setInboundURL() Methods

Note that these URLs are now resolved relative to the context server. For example, if the project directory for the context server is test, then the following inputs are valid and equivalent: jsxapp://test/xml/typical.xml
xml/typical.xml
JSXAPPS/test/xml/typical.xml
If the test project directory is nested in a subdirectory, such as JSXAPPS/samples/test, then the following inputs are valid and equivalent: jsxapp://samples/test/xml/typical.xml
samples/test/xml/typical.xml
JSXAPPS/samples/test/xml/typical.xml