[
https://issues.apache.org/jira/browse/UIMA-1810?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Marshall Schor closed UIMA-1810.
Resolution: Fixed
> Website link to Subclipse installation site is out of date
> ---
[
https://issues.apache.org/jira/browse/UIMA-1813?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Marshall Schor closed UIMA-1813.
Resolution: Fixed
> aggregate parent pom build fails rat test
>
aggregate parent pom build fails rat test
-
Key: UIMA-1813
URL: https://issues.apache.org/jira/browse/UIMA-1813
Project: UIMA
Issue Type: Bug
Components: Build, Packaging and Test
> Seems that an easy work-around would be to have your reader and writer
> threads synchronize on their access to the CAS. If we implemented
> concurrent access, this is what we would have to do, inside the CAS
> itself.
>
> When new data are added to the CAS, indexes are often updated. If thes
On 6/16/2010 10:22 AM, Erwan Moreau wrote:
> Hi,
>
> Thanks for the answer.
>
>
>> Hi,
>>
>> The CAS is not designed for concurrent access, to my knowledge, but
>> perhaps others can comment more on this.
>>
>>
> I'd like to know more about that, because imho this is a quite strong
> l
Hi,
Thanks for the answer.
> Hi,
>
> The CAS is not designed for concurrent access, to my knowledge, but
> perhaps others can comment more on this.
>
I'd like to know more about that, because imho this is a quite strong
limitation: maybe naively, I used to think that using concurrent access
o
