Re: CAS and Serialization on Emoji codes
I started a thread for this on the users list - please continue there. -Marshall On 9/5/2018 9:50 AM, Yuqi Zhang wrote: > Dear UIMA experts, > > I need process a String including an emoji ( > https://www.iemoji.com/view/emoji/2/smileys-people/smiling-face-with-smiling-eyes > ). > I put the string "This is a " in a CAS, and sendCAS(cas) to a remote > server. > But it failed at addMessage(msg) at line 971 in class > BaseUIMAAsynchronousEngineCommon_impl with the error message: > > javax.jms.JMSException: Failed to build body from content. Serializable > class not available to broker. Reason: java.lang.ClassNotFoundException: > Forbidden class org.xml.sax.SAXParseException! This class is not trusted to > be serialized as ObjectMessage payload. > > > When I check the serialization result of the cas in the msg, I see the > is encoded as "". > Is that the reason this CAS sent failed? > Because this emoji can be processed without any problem in my another > codes where calls the sendAndReceiveCAS(). The serialization result there > is "". > How does it happen? > Besides the sofa content, is there any other factors to affect the > serialization result? > > I am a newer to UIMA. And I have read the UIMA references about the > serialization and cas sections. But still have no idea how I could make > surely serialized into "" > > Many thanks for any feedback! > Best regards, > Yuqi Zhang >
CAS and Serialization on Emoji codes
Dear UIMA experts, I need process a String including an emoji ( https://www.iemoji.com/view/emoji/2/smileys-people/smiling-face-with-smiling-eyes ). I put the string "This is a " in a CAS, and sendCAS(cas) to a remote server. But it failed at addMessage(msg) at line 971 in class BaseUIMAAsynchronousEngineCommon_impl with the error message: javax.jms.JMSException: Failed to build body from content. Serializable class not available to broker. Reason: java.lang.ClassNotFoundException: Forbidden class org.xml.sax.SAXParseException! This class is not trusted to be serialized as ObjectMessage payload. When I check the serialization result of the cas in the msg, I see the is encoded as "". Is that the reason this CAS sent failed? Because this emoji can be processed without any problem in my another codes where calls the sendAndReceiveCAS(). The serialization result there is "". How does it happen? Besides the sofa content, is there any other factors to affect the serialization result? I am a newer to UIMA. And I have read the UIMA references about the serialization and cas sections. But still have no idea how I could make surely serialized into "" Many thanks for any feedback! Best regards, Yuqi Zhang
[jira] [Created] (UIMA-5862) RM can fail with a comparator violating its general contract
Burn Lewis created UIMA-5862: Summary: RM can fail with a comparator violating its general contract Key: UIMA-5862 URL: https://issues.apache.org/jira/browse/UIMA-5862 Project: UIMA Issue Type: Bug Components: DUCC Reporter: Burn Lewis Fix For: future-DUCC Problem is JobByTimeSorter in NodepoolScheduler -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (UIMA-5785) Ruta: short name of parent in DECLARE not resolved
[ https://issues.apache.org/jira/browse/UIMA-5785?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16604602#comment-16604602 ] Viorel Morari commented on UIMA-5785: - Added patch to allow transitive imported types in DECLARE statement (permanent resolveImports). > Ruta: short name of parent in DECLARE not resolved > -- > > Key: UIMA-5785 > URL: https://issues.apache.org/jira/browse/UIMA-5785 > Project: UIMA > Issue Type: Bug > Components: Ruta >Affects Versions: 2.6.1ruta >Reporter: Peter Klügl >Assignee: Peter Klügl >Priority: Major > Fix For: 2.6.2ruta > > Attachments: UIMA-5785.patch > > > Ruta: short name of parent in DECLARE not resolved -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (UIMA-5785) Ruta: short name of parent in DECLARE not resolved
[ https://issues.apache.org/jira/browse/UIMA-5785?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Viorel Morari updated UIMA-5785: Attachment: UIMA-5785.patch > Ruta: short name of parent in DECLARE not resolved > -- > > Key: UIMA-5785 > URL: https://issues.apache.org/jira/browse/UIMA-5785 > Project: UIMA > Issue Type: Bug > Components: Ruta >Affects Versions: 2.6.1ruta >Reporter: Peter Klügl >Assignee: Peter Klügl >Priority: Major > Fix For: 2.6.2ruta > > Attachments: UIMA-5785.patch > > > Ruta: short name of parent in DECLARE not resolved -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (UIMA-5780) Ruta: Support all SerialFormats in Query View
[ https://issues.apache.org/jira/browse/UIMA-5780?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16604580#comment-16604580 ] Viorel Morari commented on UIMA-5780: - Added patch to enable QueryView to support all SerialFormats (i.e. xmi, bcas, xcas, scas). > Ruta: Support all SerialFormats in Query View > - > > Key: UIMA-5780 > URL: https://issues.apache.org/jira/browse/UIMA-5780 > Project: UIMA > Issue Type: Improvement > Components: Ruta >Affects Versions: 2.6.1ruta >Reporter: Peter Klügl >Assignee: Peter Klügl >Priority: Major > Fix For: 2.6.2ruta > > Attachments: UIMA-5780.patch > > > Right now, only XMI is supported -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (UIMA-5780) Ruta: Support all SerialFormats in Query View
[ https://issues.apache.org/jira/browse/UIMA-5780?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Viorel Morari updated UIMA-5780: Attachment: UIMA-5780.patch > Ruta: Support all SerialFormats in Query View > - > > Key: UIMA-5780 > URL: https://issues.apache.org/jira/browse/UIMA-5780 > Project: UIMA > Issue Type: Improvement > Components: Ruta >Affects Versions: 2.6.1ruta >Reporter: Peter Klügl >Assignee: Peter Klügl >Priority: Major > Fix For: 2.6.2ruta > > Attachments: UIMA-5780.patch > > > Right now, only XMI is supported -- This message was sent by Atlassian JIRA (v7.6.3#76005)
