Re: small memory footprint tradeoff configuration

Eddie Epstein wrote: Process calls to a Vinci service have always broken FS references. Same for calls thru the compatibility wrapper that allows calling colocated UIMA 1.4x annotators from Apache UIMA. Actually, I think that the compatibility wrapper does preserve FS addresses because it

Re: small memory footprint tradeoff configuration

On Tue, Feb 24, 2009 at 2:53 AM, Thilo Goetz twgo...@gmx.de wrote: I have found the discussion again that I was referring to.  It wasn't on this list, it was in the OASIS spec discussions.  Sorry about the confusion.  I don't feel at liberty to publish that conversation here, but maybe Adam

[jira] Commented: (UIMA-1245) Processing order of parent CAS different on UIMA and UIMA AS

[ https://issues.apache.org/jira/browse/UIMA-1245?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12676308#action_12676308 ] Burn Lewis commented on UIMA-1245: -- To summarize my understanding of recent discussions ...

[jira] Created: (UIMA-1294) Enable access of service's ipaddr from process Cas replies

Enable access of service's ipaddr from process Cas replies -- Key: UIMA-1294 URL: https://issues.apache.org/jira/browse/UIMA-1294 Project: UIMA Issue Type: Improvement

[jira] Commented: (UIMA-1293) Replies from remote CasMultipliers that don't always generate CASes are not handled correctly

[ https://issues.apache.org/jira/browse/UIMA-1293?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12676422#action_12676422 ] Jerry Cwiklik commented on UIMA-1293: - A remote (primitive) cas multiplier's process()

[jira] Closed: (UIMA-1194) JMX stats for UIMA AS seem inconsistent

[ https://issues.apache.org/jira/browse/UIMA-1194?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jerry Cwiklik closed UIMA-1194. --- Resolution: Fixed JMX stats for UIMA AS seem inconsistent