Importing XML Files

The XML import tool imports model definitions from XML files that comply with the schema http://org.eclipse.tigerstripe/xml/tigerstripeOutput/v1-0. This schema is included in the output from the XML Export tool. The schema should be in the same directory as the file to be imported.

Running the Import

Complete the following procedure to run an XML Import

To run an import

  1. Open your Tigerstripe Perspective and right-click on your Tigerstripe Project to which you want to import artifacts. The Import wizard displays.
  2. Select Import from the menu.
  3. Navigate to Tigerstripe/Bulk Import (xml) and click Next. The Import/update from XML wizard displays.
  4. Select the project to where you want to import the XML file, and select the XML file you want to import. In the case of a summary file and multiple artifact XML files, select the XML file to import and click Load XML File.

    A dialog box containing a list of information messages and possible errors about any differences between the project and the XML file display. You can view snippets of these messages and errors in the dialog box. To view more details, locate the file XMLBulkImport.log. which is created in the same directory where the XML file is located.

  5. After reviewing any messages, you can proceed with the file import by clicking Apply Changes. This updates the Tigerstripe Project with the information in the XML file. The message dialog box displays the information about the import.

The Import Process

When there is a difference between the XML file and the Tigerstripe model, the Import tool will update the model with the data in the XML file. The follow are exceptions:

Differences Reporting Format

Log messages for differences are formatted as shown in the following example:

Type = presence Scope = Artifact:Field Local art = com.mycompany.Entity0 Remote art = com.mycompany.Entity0 Object = aField0 LocalVal = absent RemoteVal = present

In the Information dialog box, the differences will have a short format as shown in the following example:

Artifact:Field com.mycompany.Entity0 aField0 {absent,present}

This is equivalent to the long format fields :

Scope Localart Object {LocalVal,RemoteVal}

Note: If Localart is empty (as in the special case of a new Artifact found in the project), Localart is replaced by Remoteart.


© copyright 2005, 2006, 2007 Cisco Systems, Inc. - All rights reserved