This is the process of saving the service definition to the XML file. Saving does not perform any validation. The save operation de-serializes the Service Definition object to XML and saves it to the file specified in the configuration. For more information, please see Web Services Designer Configuration.
Saving happens in the following scenarios:
· While Exiting the Personify WSD
When the Personify WSD is closed, the system prompts the user to save the
changes, if there are any unsaved changes.
o Yes – Saves the changes and exits
o No – Ignores the changes and exits
o Cancel – Does not save, does not exit, and stays open
· While Building or Checking-In
When the Service is built, the system prompts the user to save the changes
if there are any unsaved changes.
o OK – Saves the changes and proceed with the build
o Cancel – Does not save, does not proceed with the build, stays open
· On Demand Saving
The user can save the changes anytime by clicking the Save button on the
Toolbar.
Auto-recovery has not been implemented in this release. Therefore, it is recommended to save your work often to avoid the loss of work due to any unexpected happenings, such as application crash, network unavailability, operating system crash, or power failure.
See also:
· Web Services Designer Behavior
· Starting the Web Services Designer
· Designing Service Elements
o Creating New Read/Write Entities
§ File Uploading via Read/Write Entities
o Creating New Read-Only Entities
o Creating New Service Parameters
o Creating New Service Operations
· Web Services Designer Filtering and Searching Elements
· Web Services Designer Error Handling
· Validating the Service Definitions
· Modifying the Layer Name and Namespace
· Utilizing the Visual Behaviors of the Canvas
· Working with the Element Attributes (Properties Pane)
· Configuring Personify API Validation Issues
· Refreshing the Service Definitions
· Enabling and Disabling Entities
· Exposing Data Services for Data Export / Import