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
The XML source view provides a nice overview over the subtree of a node, if you have to work with XML anyway (e.g. when working with AEM packages). A nice extension would be if it was possible to edit a subtree within that XML view: make changes in the XML with a text editor in the browser and save it, so that the Composum Browser can update the subtree accordingly. Or copy it out into an XML editor, change it, and later copy it back into the browser again and save it.
An interesting point is how to deal with the special JCR attributes like jcr:uuid , jcr:created, jcr:createdBy and so forth, which are omitted in the XML view. It probably makes sense to omit those, and leave these unchanged when the XML is saved back into the JCR. For this, it would be neccesary to merge the edited XML with the existing JCR tree, and update existing nodes, instead of deleting the old nodes and creating new ines.
The text was updated successfully, but these errors were encountered:
The XML source view provides a nice overview over the subtree of a node, if you have to work with XML anyway (e.g. when working with AEM packages). A nice extension would be if it was possible to edit a subtree within that XML view: make changes in the XML with a text editor in the browser and save it, so that the Composum Browser can update the subtree accordingly. Or copy it out into an XML editor, change it, and later copy it back into the browser again and save it.
An interesting point is how to deal with the special JCR attributes like jcr:uuid , jcr:created, jcr:createdBy and so forth, which are omitted in the XML view. It probably makes sense to omit those, and leave these unchanged when the XML is saved back into the JCR. For this, it would be neccesary to merge the edited XML with the existing JCR tree, and update existing nodes, instead of deleting the old nodes and creating new ines.
The text was updated successfully, but these errors were encountered: