I've created JIRA for this: https://issues.apache.org/jira/browse/UIMA-5791
Not yet sure how to fix this. Will take a look next week. If I understand
the requirements right, the default encoding should be UTF-8 when
deserializing service metadata..
There should also be a way to override the default
Jerry Cwiklik created UIMA-5791:
---
Summary: UIMA-AS: fix client SAXParseException when deserializing
metadata
Key: UIMA-5791
URL: https://issues.apache.org/jira/browse/UIMA-5791
Project: UIMA
I
Marshall Schor created UIMA-5790:
Summary: ConceptMapper (addon) use of FileXXStream should do
appropriate buffering
Key: UIMA-5790
URL: https://issues.apache.org/jira/browse/UIMA-5790
Project: UIMA
Recently, we debugged an issue where a user had a UIMA-AS client running on
Windows, connecting to a UIMA-AS service running on Linux in the cloud.
The linux box was set up with LANG etc set to UTF-8. Windows did not have any
special configuration.
After a successful service deployment on Li
