Skip to content

Refactoring

Johannes Heucher edited this page Oct 12, 2022 · 3 revisions

Refactoring across Applications

Performing Refactorings

Use the refactoring mechanisms of Xyna Factory whenever possible, since Xyna Factory is taking care of dependencies. Do not modify the xml files in the file system manually!
The following options for refactoring in the Factory Navigation exist:

  • Move Workflows, Datatypes, Exceptions and Service Groups
  • Rename Datatype, Workflows, etc. as desired e.g. to match new project naming conventions, to precise naming, to be more specific.
Usability hint: Use Xyna Application to create backup versions during refactoring.
Usability hint: Avoid the usage of reserved keywords, e.g. interface, class, integer, …. Usually these words will be escaped by the Factory by appropriate pre- and postfixes.

Splitting of Applications

Separation of entities into dependent Applications. This could be an advantage if different parts of the Application should be versioned and delivered separately.
In general the usage of dependent Application is indicated by

  • Generated XMOM data type from an XSD
  • Interface definition
  • Functional components: e.g. protocol implementations
Splitting procedure
  1. Define a new Application Definition in the Workspace.
  2. Add all objects to the Application Definition that should be moved to the dependent Application.
  3. Build an Application Version.
  4. Link the new Application to the Workspace as a dependent Application.
  5. Conflicts will be reported since objects are now duplicates in the Workspace and the linked Application. Remove conflicts by delete these objects in the Workspace.
  6. The original Application Definition is now empty, since all objects are removed. Remove the Application Definition.
  7. To continue the development of the dependent Application, import the Application into a new separate Workspace. The dependent Application should not be imported into the original Workspace!
Clone this wiki locally