[jira] [Reopened] (UIMA-3569) Allow extensions for complete block constructs in Ruta
[ https://issues.apache.org/jira/browse/UIMA-3569?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Peter Klügl reopened UIMA-3569: --- missed to commit example project of branch Allow extensions for complete block constructs in Ruta -- Key: UIMA-3569 URL: https://issues.apache.org/jira/browse/UIMA-3569 Project: UIMA Issue Type: New Feature Components: ruta Affects Versions: 2.2.0ruta Reporter: Peter Klügl Assignee: Peter Klügl Fix For: 2.2.0ruta Allow extensions for complete block constructs in Ruta. This means essentially that the lanaguge can be extended with additional constructs that define an specific syntax and change the apporach of rule inference. This would easy the development and integration of new functionlity like FSTs or similar compiled versions of rule sets. (Students could develop FST implementations or similar stuff without changing the ruta code itself) -- This message was sent by Atlassian JIRA (v6.1.5#6160)
[jira] [Closed] (UIMA-3569) Allow extensions for complete block constructs in Ruta
[ https://issues.apache.org/jira/browse/UIMA-3569?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Peter Klügl closed UIMA-3569. - Resolution: Fixed fixed Allow extensions for complete block constructs in Ruta -- Key: UIMA-3569 URL: https://issues.apache.org/jira/browse/UIMA-3569 Project: UIMA Issue Type: New Feature Components: ruta Affects Versions: 2.2.0ruta Reporter: Peter Klügl Assignee: Peter Klügl Fix For: 2.2.0ruta Allow extensions for complete block constructs in Ruta. This means essentially that the lanaguge can be extended with additional constructs that define an specific syntax and change the apporach of rule inference. This would easy the development and integration of new functionlity like FSTs or similar compiled versions of rule sets. (Students could develop FST implementations or similar stuff without changing the ruta code itself) -- This message was sent by Atlassian JIRA (v6.1.5#6160)
[jira] [Resolved] (UIMA-3654) Better error message when fixed flow constraint has error
[ https://issues.apache.org/jira/browse/UIMA-3654?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Marshall Schor resolved UIMA-3654. -- Resolution: Fixed Better error message when fixed flow constraint has error - Key: UIMA-3654 URL: https://issues.apache.org/jira/browse/UIMA-3654 Project: UIMA Issue Type: Improvement Components: Core Java Framework Affects Versions: 2.5.0SDK Reporter: Marshall Schor Assignee: Marshall Schor Priority: Minor Fix For: 2.5.1SDK When running with the usual fixed flow controller, it works from a list of flow targets, each name which must match a delegate analysis engine key. Add a check and error message if one of these names doesn't match any delegate key. -- This message was sent by Atlassian JIRA (v6.1.5#6160)
[jira] [Created] (UIMA-3655) CasPool incorrectly stores references to the InitialView of each CAS
Eddie Epstein created UIMA-3655: --- Summary: CasPool incorrectly stores references to the InitialView of each CAS Key: UIMA-3655 URL: https://issues.apache.org/jira/browse/UIMA-3655 Project: UIMA Issue Type: Bug Components: Core Java Framework Reporter: Eddie Epstein Assignee: Marshall Schor For cas pools, getCas returns a handle to the InitialView of an empty CAS, and stores this handle to match in releaseCas. This breaks for services that employ sofamapping. The empty CAS is filled from a serialized CAS sent to the service. It is possible that a CAS received may not contain the view, CAS.NAME_DEFAULT_SOFA, specified by sofamapping. Then, when the service tries to return the CAS to the pool, releaseCas blows up at the first line, CAS cas = aCas.getView(CAS.NAME_DEFAULT_SOFA); so the CAS is not returned to the pool == CAS leak. The cas pool should be storing references to the base CAS, which is independent of views. -- This message was sent by Atlassian JIRA (v6.1.5#6160)
