You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@uima.apache.org by "Eddie Epstein (JIRA)" <ui...@incubator.apache.org> on 2007/01/16 16:30:27 UTC
[jira] Resolved: (UIMA-187) getSofaDataString() is documented in
the manual but does not exist in the code
[ https://issues.apache.org/jira/browse/UIMA-187?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Eddie Epstein resolved UIMA-187.
--------------------------------
Resolution: Fixed
> getSofaDataString() is documented in the manual but does not exist in the code
> ------------------------------------------------------------------------------
>
> Key: UIMA-187
> URL: https://issues.apache.org/jira/browse/UIMA-187
> Project: UIMA
> Issue Type: Bug
> Components: Core Java Framework
> Reporter: Adam Lally
> Assigned To: Eddie Epstein
> Fix For: 2.1
>
>
> It's exactly equivalent to getDocumentText() but I would vote to add it for consistency.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: https://issues.apache.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
Re: [jira] Resolved: (UIMA-187) getSofaDataString() is documented in the manual but does not exist in the code
Posted by Eddie Epstein <ea...@gmail.com>.
On 1/16/07, Marshall Schor <ms...@schor.com> wrote:
> I see this API was added to the CAS, but was not added to the JCas. Is
> there a reason we would update the CAS API, and not do the corresponding
> update in the JCas API?
What is JCas again?
> (Other than, of course, that my suggested "refactoring" was vetoed, and
> now we have to remember to think about these things ourselves ;-) )?
Yup, this remains a problem.
Method added to JCas.
Eddie
Re: [jira] Resolved: (UIMA-187) getSofaDataString() is documented
in the manual but does not exist in the code
Posted by Marshall Schor <ms...@schor.com>.
Eddie Epstein (JIRA) wrote:
> [ https://issues.apache.org/jira/browse/UIMA-187?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
>
> Eddie Epstein resolved UIMA-187.
> --------------------------------
>
I see this API was added to the CAS, but was not added to the JCas. Is
there a reason we would update the CAS API, and not do the corresponding
update in the JCas API?
(Other than, of course, that my suggested "refactoring" was vetoed, and
now we have to remember to think about these things ourselves ;-) )?
-Marshall