You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@uima.apache.org by "Adam Lally (JIRA)" <ui...@incubator.apache.org> on 2007/06/21 23:30:25 UTC

[jira] Resolved: (UIMA-443) fix flow ResultSpec handling

     [ https://issues.apache.org/jira/browse/UIMA-443?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Adam Lally resolved UIMA-443.
-----------------------------

    Resolution: Fixed
      Assignee: Michael Baessler  (was: Adam Lally)

I believe I've fixed this.  I added a test case based on the example Michael posted to uima-dev.

Michael, please double-check.

> fix flow ResultSpec handling
> ----------------------------
>
>                 Key: UIMA-443
>                 URL: https://issues.apache.org/jira/browse/UIMA-443
>             Project: UIMA
>          Issue Type: Bug
>          Components: Core Java Framework
>    Affects Versions: 2.1
>            Reporter: Michael Baessler
>            Assignee: Michael Baessler
>             Fix For: 2.2
>
>
> Currently it is possible to set a result spec for a flow node AnalysisSequenceCapabilityNode.setResultSpec(). But it seems that this feature is never supported in UIMA 2.x. We should either remove/deprecate this APIs if this is really true that it is never supported.
> But I think that this was a very important feature for search engine integrations, so I would vote for adding this functionality again to the FlowController stuff. Let's start the discussion on how this can be done and what we will do for UIMA 2.2.

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.