Rational Developer for Power Systems Software

Class ApplicationDiagramMigration

  extended by com.ibm.etools.systems.application.visual.editor.resources.ApplicationDiagramMigration

public class ApplicationDiagramMigration
extends Object

This class is used to migrate the application model and diagram files from pervious versions to the current version. Currently supported model version is 2.0. Migrating just the application model file is relatively straight forward. However migrating the diagram file in conjunction with the model file because the diagram file maintains XPath expressions that reference elements within the model file and these have to be maintained during migration.

Field Summary
static String copyright
Constructor Summary
ApplicationDiagramMigration(IFile inputIFile, boolean diagramAvailable)
Method Summary
static boolean isIncompatibleModelException(Throwable e)
          Helper method to determine if an exception is related to an incompatible model format
 boolean migrate(IEditorPart editor)
          Mirate the model and diagram files.
Methods inherited from class java.lang.Object
clone, equals, finalize, getClass, hashCode, notify, notifyAll, toString, wait, wait, wait

Field Detail


public static final String copyright
See Also:
Constant Field Values
Constructor Detail


public ApplicationDiagramMigration(IFile inputIFile,
                                   boolean diagramAvailable)

Method Detail


public boolean migrate(IEditorPart editor)
Mirate the model and diagram files.


public static boolean isIncompatibleModelException(Throwable e)
Helper method to determine if an exception is related to an incompatible model format

Rational Developer for Power Systems Software

Copyright 2011 IBM Corp. All Rights Reserved.

Note: This documentation is for part of an interim API that is still under development and expected to change significantly before reaching stability. It is being made available at this early stage to solicit feedback from pioneering adopters on the understanding that any code that uses this API will almost certainly be broken (repeatedly) as the API evolves.