[
https://issues.apache.org/jira/browse/UIMA-2409?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Marshall Schor resolved UIMA-2409.
----------------------------------
Resolution: Fixed
The code that disallowed copying between 2 views of the same CAS was removed.
Copying from v1 to v1 (same view) throws concurrent modification exception. I
think that's OK. Copying from v1 to v2 of the same CAS seems to work. If the
sofa data isn't copied, any types that are subtypes of AnnotationBase will have
begin/end potentially pointing to meaningless places (if the sofa data is
different). I think this is a user beware condition. What motivated this was
that the previous restrictions started breaking some user code which was
copying a (non-annotation) between views - that should be OK.
> CasCopier.copyCasView should be able to copy into a view with a different name
> ------------------------------------------------------------------------------
>
> Key: UIMA-2409
> URL: https://issues.apache.org/jira/browse/UIMA-2409
> Project: UIMA
> Issue Type: Improvement
> Components: Core Java Framework
> Reporter: Joern Kottmann
> Assignee: Marshall Schor
> Priority: Trivial
> Fix For: 2.4.1SDK
>
> Attachments: UIMA-2409.patch
>
>
> The CasCopier should be able to copy a CAS view into a new CAS and giving
> this new CAS view a different name.
> A common use case is to copy a view of multi view CAS into a new single view
> CAS.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
