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/06 16:44:26 UTC
[jira] Created: (UIMA-437) Annotators are not prevented from
calling CAS.release()
Annotators are not prevented from calling CAS.release()
--------------------------------------------------------
Key: UIMA-437
URL: https://issues.apache.org/jira/browse/UIMA-437
Project: UIMA
Issue Type: Bug
Components: Core Java Framework
Reporter: Adam Lally
Assignee: Marshall Schor
Fix For: 2.2
Annotators are prohibited from calling CAS.reset() but not CAS.release().
Since release() in turn calls reset(), previously this was effectively prohibited as well. However, Marshall undid that in his recent work - making release() "unlock" the CAS prohibited functions.
This was done to allow CAS Mutipliers to release the CAS - which we currently say is a best practice when an error occurs in a CAS Multiplier.
So I think CAS Multipliers need to be allowed to call release() on CASes that they obtain from the CAS pool. But analysis components (either annotators or CAS multipliers) should not be allowed to release() CASes passed to their process() methods.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
Re: [jira] Created: (UIMA-437) Annotators are not prevented from
calling CAS.release()
Posted by Marshall Schor <ms...@schor.com>.
+1 sounds right to me.. -Marshall
Adam Lally (JIRA) wrote:
> Annotators are not prevented from calling CAS.release()
> --------------------------------------------------------
>
> Key: UIMA-437
> URL: https://issues.apache.org/jira/browse/UIMA-437
> Project: UIMA
> Issue Type: Bug
> Components: Core Java Framework
> Reporter: Adam Lally
> Assignee: Marshall Schor
> Fix For: 2.2
>
>
> Annotators are prohibited from calling CAS.reset() but not CAS.release().
>
> Since release() in turn calls reset(), previously this was effectively prohibited as well. However, Marshall undid that in his recent work - making release() "unlock" the CAS prohibited functions.
>
> This was done to allow CAS Mutipliers to release the CAS - which we currently say is a best practice when an error occurs in a CAS Multiplier.
>
> So I think CAS Multipliers need to be allowed to call release() on CASes that they obtain from the CAS pool. But analysis components (either annotators or CAS multipliers) should not be allowed to release() CASes passed to their process() methods.
>
>
[jira] Closed: (UIMA-437) Annotators are not prevented from calling
CAS.release()
Posted by "Adam Lally (JIRA)" <ui...@incubator.apache.org>.
[ https://issues.apache.org/jira/browse/UIMA-437?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Adam Lally closed UIMA-437.
---------------------------
Resolution: Fixed
Fixed.
Also discovered and fixed a bug that was causing CASes released by a CAS multiplier to still be counted against its total number of checked out CASes, used for error checking purposes.
> Annotators are not prevented from calling CAS.release()
> --------------------------------------------------------
>
> Key: UIMA-437
> URL: https://issues.apache.org/jira/browse/UIMA-437
> Project: UIMA
> Issue Type: Bug
> Components: Core Java Framework
> Reporter: Adam Lally
> Assignee: Adam Lally
> Fix For: 2.2
>
>
> Annotators are prohibited from calling CAS.reset() but not CAS.release().
> Since release() in turn calls reset(), previously this was effectively prohibited as well. However, Marshall undid that in his recent work - making release() "unlock" the CAS prohibited functions.
> This was done to allow CAS Mutipliers to release the CAS - which we currently say is a best practice when an error occurs in a CAS Multiplier.
> So I think CAS Multipliers need to be allowed to call release() on CASes that they obtain from the CAS pool. But analysis components (either annotators or CAS multipliers) should not be allowed to release() CASes passed to their process() methods.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Assigned: (UIMA-437) Annotators are not prevented from
calling CAS.release()
Posted by "Adam Lally (JIRA)" <ui...@incubator.apache.org>.
[ https://issues.apache.org/jira/browse/UIMA-437?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Adam Lally reassigned UIMA-437:
-------------------------------
Assignee: Adam Lally (was: Marshall Schor)
> Annotators are not prevented from calling CAS.release()
> --------------------------------------------------------
>
> Key: UIMA-437
> URL: https://issues.apache.org/jira/browse/UIMA-437
> Project: UIMA
> Issue Type: Bug
> Components: Core Java Framework
> Reporter: Adam Lally
> Assignee: Adam Lally
> Fix For: 2.2
>
>
> Annotators are prohibited from calling CAS.reset() but not CAS.release().
> Since release() in turn calls reset(), previously this was effectively prohibited as well. However, Marshall undid that in his recent work - making release() "unlock" the CAS prohibited functions.
> This was done to allow CAS Mutipliers to release the CAS - which we currently say is a best practice when an error occurs in a CAS Multiplier.
> So I think CAS Multipliers need to be allowed to call release() on CASes that they obtain from the CAS pool. But analysis components (either annotators or CAS multipliers) should not be allowed to release() CASes passed to their process() methods.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.