Re: UIMA-AS: non-XML char in text raises SAXParseException

2011-10-24 Thread Charles Bearden
On 10/21/2011 03:17 PM, Marshall Schor wrote: also, see the comments here: https://issues.apache.org/jira/browse/UIMA-387 Thanks for your replies. And now that I actually look at the RunRemoteAsyncAE.java code, I see the command line arg ('-b') that I should be able to use with runRemoteAsyn

Re: UIMA-AS: non-XML char in text raises SAXParseException

2011-10-21 Thread Marshall Schor
also, see the comments here: https://issues.apache.org/jira/browse/UIMA-387 On 10/21/2011 1:58 PM, Charles Bearden wrote: > I created a simple UIMA-AS pipeline comprising a collection reader and an > aggregate AE, which I ran simply like so: > > runRemoteAsyncAE.sh tcp://localhost:61616 Collectio

Re: UIMA-AS: non-XML char in text raises SAXParseException

2011-10-21 Thread Marshall Schor
If you're using various "defaults", the serialization used is "XMI" , which, indeed, does require that text data being serialized be valid XML characters. And I see this is what's being used , from the backtrace. If you need to use UIMA-AS with invalid chars, you can do one of several things: 1)

UIMA-AS: non-XML char in text raises SAXParseException

2011-10-21 Thread Charles Bearden
I created a simple UIMA-AS pipeline comprising a collection reader and an aggregate AE, which I ran simply like so: runRemoteAsyncAE.sh tcp://localhost:61616 CollectionReader \ -d \ -c \ Evidently, the content I wish to process has some non-XML characters in it, because a certain bit of