Details
-
Feature
-
Status: Released (View Workflow)
-
Minor
-
Resolution: Fixed
-
1.13.2
-
None
Description
Current Situation
- XML editing
- The XML configuration can only be edited using the Tree operations or an Import file functionallity. The existing Show XML function does not support the edit operation.
- Validation
- The validation error message from the web services provides the raw SAXParseException message. In some cases it is very dificult to identify exactly in which element an error has occured.
- The currently used .xsd schema is not directly visible for users.
- Management of the custom .xsd based configurations is not supported.
Desired Behaviour
- XML editing
- The Edit XML functionality should allow direct changes to a given configuration and support the following features:
- XML syntax highlighting
- Submit a configuration. The configuration does not have to be complete and can be edited later.
- Validation against the given xsd schema to check for completion and highlight the relevant lines/elements on errors
- The Edit XML functionality should allow direct changes to a given configuration and support the following features:
- Validation
- The full path to the error element should be automatically expanded in the tree to show the element data in the right hand panel or to show the missing child elements.
- The assigned .xsd schema file should be available to the download or to be shown in the browser window.
- Custom configurations
- The Others functionality of the XML Editor should allow management of the .xsd based configurations.
- Schema assigment
- from a http(s) address
- from a user's local file system and
- from a local file on the system where the JOC Cockpit is installed
- It should be possible to reassign an assigned schema.
- Import/Export the XML configurations
- Rename the configuration name on the tab header double click
- Delete a configuration
Attachments
There are no Sub-Tasks for this issue.