-
-
Notifications
You must be signed in to change notification settings - Fork 4
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Package Manager: File "cannot be stored" (when contains Unicode?) #14
Comments
|
In the past we had another issue where a XAR generated by exude contained an illegal XML construct making it impossible to reinstall the XAR file. Not sure which ticket however... |
@duncdrum, thanks for commenting. I looked, but can't find any evidence that the em dash is illegal in XML comments. Are you able to find any? |
@TurekBot I was wrong, In any case a clearer error message when dealing with perceived well-formedness still sounds the way to go. |
I ran into this error when I tried to upload an app I made to a new eXist install.
What is the problem
When I try to upload the .xar archive via the Package Manager, everything works except it won't store just one certain file.
After some testing, I narrowed the culprit in that file to an em dash (—) inside of a comment.
When the em dash is there, I get the error; when there's no em dash, no error.
Here's the part of the file in question. (Scroll over to see the em dash.)
I think this is the line that throws the exception: https://github.com/eXist-db/exist/blob/1095e49769c5edfefdde022678e65755d5f00e8c/exist-core/src/main/java/org/exist/repo/Deployment.java#L807
Here's the important section of exist.log when the error is thrown.
What did you expect
I expected any unicode symbol to be valid XML, since XML's default encoding is UTF-8, but maybe it's not related to unicode at all. I checked the XSL file against various validators, and it appears to be well-formed.
Describe how to reproduce or add a test
Try to upload this package with an em dash (with the file that has an em dash)
Notice the error. ("Deployment incomplete, 1 issues found: replace-email.xsl: replace-email.xsl cannot be stored")
Try to upload this package without an em dash (everything the same, but no em dash)
Notice that everything is stored as expected.
Context information
The text was updated successfully, but these errors were encountered: