[jira] Created: (UIMA-1063) Incorrect push/pop used in JNI code
Incorrect push/pop used in JNI code - Key: UIMA-1063 URL: https://issues.apache.org/jira/browse/UIMA-1063 Project: UIMA Issue Type: Bug Components: C++ Framework Reporter: Eddie Epstein Assignee: Eddie Epstein Fix For: 2.2C PushLocalFrame/PopLocalFrame are incorrectly used when transferring CAS data from the native environment to Java. These cause the newly created Java arrays to be marked for GC, which can (and sometimes does!) take place before the native routine has returned the reference to the new array to Java. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Closed: (UIMA-1039) Fix use of non thread safe calls service wrapper Update property names in reply message to be compatible with Java.
[ https://issues.apache.org/jira/browse/UIMA-1039?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Eddie Epstein closed UIMA-1039. --- Resolution: Fixed Fix use of non thread safe calls service wrapper Update property names in reply message to be compatible with Java. -- Key: UIMA-1039 URL: https://issues.apache.org/jira/browse/UIMA-1039 Project: UIMA Issue Type: Bug Components: C++ Framework Reporter: Bhavani Iyer Assignee: Bhavani Iyer Fix For: 2.2C Attachments: UMA-1039-1.patch, UMA-1039.patch Call to uimacpp logger is not thread safe. Rename property TimeInAnalytic to TimeInProcessCas in reply message Add support for time to send reply messaage to the JMX statistics maintained by the wrapper. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Created: (UIMA-1064) Clarify uimacpp build environment and dependencies
Clarify uimacpp build environment and dependencies -- Key: UIMA-1064 URL: https://issues.apache.org/jira/browse/UIMA-1064 Project: UIMA Issue Type: Bug Components: C++ Framework Reporter: Eddie Epstein Assignee: Eddie Epstein Fix For: 2.2C -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
UIMA-AS release candidate 06 ready for testing
This candidate should be identical with the 05, with the exception of fixing 3 error messages which were using the wrong resource bundle keys, and the inclusion of the export classification in the READMEs. I hope we can conclude testing this week and tentatively plan to post a vote to approve release next Monday or so. -Marshall
[jira] Created: (UIMA-1065) CFE - configurable feature extrator for UIMA annotation comparison, evaluation, testing, generation of machine learning features
CFE - configurable feature extrator for UIMA annotation comparison, evaluation, testing, generation of machine learning features Key: UIMA-1065 URL: https://issues.apache.org/jira/browse/UIMA-1065 Project: UIMA Issue Type: New Feature Components: Tools Reporter: Igor Sominsky Priority: Minor CFE - configurable feature extrator for UIMA annotation comparison, evaluation of performance metrics such as precision/recall/f-score, regression testing, generation of machine learning features. It provides Feature Extraction Specification language (FESL), that specifies rules for feature extraction. The criteria for the extraction could be customized by multiple conditions written in FESL in normal disjunctive form. Extracted features can be output into a file or CAS. Extractor can be implemented as CAS consumer of TAE -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Updated: (UIMA-1065) CFE - configurable feature extrator for UIMA annotation comparison, evaluation, testing, generation of machine learning features
[ https://issues.apache.org/jira/browse/UIMA-1065?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Igor Sominsky updated UIMA-1065: Attachment: CFE.zip.md5 CFE.zip CFE - configurable feature extrator for UIMA annotation comparison, evaluation, testing, generation of machine learning features Key: UIMA-1065 URL: https://issues.apache.org/jira/browse/UIMA-1065 Project: UIMA Issue Type: New Feature Components: Tools Reporter: Igor Sominsky Priority: Minor Attachments: CFE.zip, CFE.zip.md5 CFE - configurable feature extrator for UIMA annotation comparison, evaluation of performance metrics such as precision/recall/f-score, regression testing, generation of machine learning features. It provides Feature Extraction Specification language (FESL), that specifies rules for feature extraction. The criteria for the extraction could be customized by multiple conditions written in FESL in normal disjunctive form. Extracted features can be output into a file or CAS. Extractor can be implemented as CAS consumer of TAE -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
SaxParserException
Hello UIMA Developers,I am getting the following error when I run the UIMA Document Analyzer. However, If I use the interactive mode it works fine. I can't specify what is the source file of this issue. I would appreciate any help. Thanks, Ahmed Caused by: org.xml.sax.SAXParseException: Trying to serialize non-XML 1.0 character: , 0x0 at org.apache.uima.util.XMLSerializer$CharacterValidatingContentHandler.checkForInvalidXmlChars( XMLSerializer.java:235) at org.apache.uima.util.XMLSerializer$CharacterValidatingContentHandler.startElement( XMLSerializer.java:155) at org.apache.uima.cas.impl.XmiCasSerializer$XmiCasDocSerializer.startElement( XmiCasSerializer.java:839) at org.apache.uima.cas.impl.XmiCasSerializer$XmiCasDocSerializer.encodeFS( XmiCasSerializer.java:592) at org.apache.uima.cas.impl.XmiCasSerializer$XmiCasDocSerializer.encodeIndexed( XmiCasSerializer.java:537) at org.apache.uima.cas.impl.XmiCasSerializer$XmiCasDocSerializer.serialize( XmiCasSerializer.java:221) at org.apache.uima.cas.impl.XmiCasSerializer$XmiCasDocSerializer.access$500( XmiCasSerializer.java:99) at org.apache.uima.cas.impl.XmiCasSerializer.serialize( XmiCasSerializer.java:1324) at org.apache.uima.cas.impl.XmiCasSerializer.serialize( XmiCasSerializer.java:1304) at org.apache.uima.tools.components.XmiWriterCasConsumer.writeXmi( XmiWriterCasConsumer.java:146) at org.apache.uima.tools.components.XmiWriterCasConsumer.processCas( XmiWriterCasConsumer.java:118) ... 10 more
[jira] Updated: (UIMA-1066) Incorrect property name TimeInProcessCAS in reply message
[ https://issues.apache.org/jira/browse/UIMA-1066?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Bhavani Iyer updated UIMA-1066: --- Attachment: UIMA-1066.patch Incorrect property name TimeInProcessCAS in reply message - Key: UIMA-1066 URL: https://issues.apache.org/jira/browse/UIMA-1066 Project: UIMA Issue Type: Bug Reporter: Bhavani Iyer Attachments: UIMA-1066.patch TimeInProcessCAS has incorrect case. Look up is case sensitive. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
Re: SaxParserException
Ahmed Abdeen(Home) wrote: Hello UIMA Developers,I am getting the following error when I run the UIMA Document Analyzer. However, If I use the interactive mode it works fine. I can't specify what is the source file of this issue. I would appreciate any help. Thanks, Ahmed Please see http://incubator.apache.org/uima/downloads/releaseDocs/2.2.2-incubating/docs/html/tutorials_and_users_guides/tutorials_and_users_guides.html#ugr.tug.xmi_emf.xml_character_issues It appears that some String data which is being serialized has invalid character codes in it (from an XML viewpoint) - namely a x'00'. There are several things you can do. 1) don't serialize this in the cas consumer. You may not realize this, but the Document Analyzer puts a cas consumer following your annotator, for the purpose of serializing out the processed data. If you write your own UIMA application, and don't use the Document Analyzer tool, you can choose what to write out and whether or not to use the XML serialization. 2) If it is acceptable in your application, you can change the invalid data to some alternate valid data. This change would of course depend on your application requirements. Does this answer your question? -Marshall
