You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
User Story
When the XSD Validation fails we want to return the XPath Expression to the Element that caused the failure.
This way the front-end can directly open an edit wizard so a Engineer can fix the issue easily.
Build steps
Change validation using the String to first create a Document object and use this for validation
Change the validation according to URL mention by additional information to get the Node/Element by a Validation Error
Convert this Node to a unique XPath expression to find the Element later in the document. (Tip: We can check how OpenSCD converts Elements to CSS Selectors for each element.)
Extend the Validation Response with an extra element 'xpath' to put the XPAth Expression in. If there is no Element/XPath Expression to be created this value will just be null.
Acceptance criteria
Additional information
The idea is to first see if we can get this working for the XSD Validation part and if this works successful in the front-end also discuss if something similar is possible from the OCL Rules (RiseClipse)
User Story
When the XSD Validation fails we want to return the XPath Expression to the Element that caused the failure.
This way the front-end can directly open an edit wizard so a Engineer can fix the issue easily.
Build steps
Acceptance criteria
Additional information
The idea is to first see if we can get this working for the XSD Validation part and if this works successful in the front-end also discuss if something similar is possible from the OCL Rules (RiseClipse)
For the Schema validation I found a possible solution to get the Element/Node in the Error Handler.
https://stackoverflow.com/questions/67500546/java-xsd-validator-get-the-node-of-the-element-containing-the-validation-err
The next step will be to convert this Node to a XPath Expression that can be used by the front-end.
See #108 for more information about the small investigation.
The text was updated successfully, but these errors were encountered: