TWCable
Filter trying to write invalid characters
Even though a Node name may not meet the JCR specification, it is still possible (especially for content migrated from old CQ instances) for bad data to come over.
Grabbit should either filter (not write) bad nodes while logging the error, rewrite the name/property to something legal while logging the error, or fail with a clearer error message.
See GH-114
https://jackrabbit.apache.org/api/1.4/org/apache/jackrabbit/util/Text.html#escapeIllegalJcrChars(java.lang.String) Potentially for reference
Hi @jbornemann I've tried rewriting the name in ProtoNodeDecorator#getOrCreateNode(Session) method, using https://jackrabbit.apache.org/api/1.4/org/apache/jackrabbit/util/Text.html#escapeIllegalJcrChars(java.lang.String), as well as with https://docs.adobe.com/content/docs/en/cq/5-6-1/javadoc/com/day/cq/commons/jcr/JcrUtil.html#createValidName(java.lang.String)
One issue i found with Text#escapeIllegalJcrChars is it will escape colon(:) as well, so a jcr:content node will be written as jcr%3Acontent in repository. Additionally, JcrUtil#createValidName will not be much useful either, as it converts a dot(.) and colon(:) into an underscore(_), as in a default.groovy will become default_groovy.
Should i write my own method which will filter only the needed characters viz "[, ]" as given in #114 and may be some others as well ?
Funny enough, that method isn't wrong, in fact ':' is technically an invalid name character according to the spec, and Jackrabbit even admits so in https://wiki.apache.org/jackrabbit/EncodingAndEscaping; however in AEM we freely use it in things like jcr:content, and Jackrabbit seems to not restrict it's use. According to the spec, if you want to use ':', or '[' in your JCR implementation, you are supposed to map these restricted characters to special private-use code points defined in the spec.
Anyways, since we don't really understand the root cause of this issue, or really if there is a practical issue at all; since we support > CQ 5.6; I would vote no-action on this issue.
I think its ok to keep this issue open (in-case we have cases where there is bad data already in AEM 6.x instances and then Grabbit is used to sync) .. but as Jeff said, we may probably not take any action on this right now ..
