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 2006/12/20 17:31:21 UTC

[jira] Created: (UIMA-134) Extend CasCopier to support multiple views

Extend CasCopier to support multiple views
------------------------------------------

                 Key: UIMA-134
                 URL: http://issues.apache.org/jira/browse/UIMA-134
             Project: UIMA
          Issue Type: Improvement
          Components: Core Java Framework
            Reporter: Adam Lally
         Assigned To: Adam Lally
            Priority: Minor


The CasCopier utility class should support multiple views/Sofas.

1) There should be a way to copy multiple views in the source CAS, each to its own view in the target CAS, while keeping a "memory" of copied FS so duplicates are not created.

2) References to Sofas need to be preserved in the target CAS.  If we copy a source FS referencing a Sofa with SofaID "Foo" then this should result in a reference to the Sofa with the same SofaID in the target CAS.  If that Sofa does not exist, we can either create it or throw an exception (probably this should be determined by an agument to the method call).

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: http://issues.apache.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira

        

[jira] Closed: (UIMA-134) Extend CasCopier to support multiple views

Posted by "Adam Lally (JIRA)" <ui...@incubator.apache.org>.
     [ https://issues.apache.org/jira/browse/UIMA-134?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Adam Lally closed UIMA-134.
---------------------------


This has gotten through significant testing by a user, closing.

> Extend CasCopier to support multiple views
> ------------------------------------------
>
>                 Key: UIMA-134
>                 URL: https://issues.apache.org/jira/browse/UIMA-134
>             Project: UIMA
>          Issue Type: Improvement
>          Components: Core Java Framework
>            Reporter: Adam Lally
>         Assigned To: Eddie Epstein
>            Priority: Minor
>             Fix For: 2.1
>
>
> The CasCopier utility class should support multiple views/Sofas.
> 1) There should be a way to copy multiple views in the source CAS, each to its own view in the target CAS, while keeping a "memory" of copied FS so duplicates are not created.
> 2) References to Sofas need to be preserved in the target CAS.  If we copy a source FS referencing a Sofa with SofaID "Foo" then this should result in a reference to the Sofa with the same SofaID in the target CAS.  If that Sofa does not exist, we can either create it or throw an exception (probably this should be determined by an agument to the method call).

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


[jira] Work started: (UIMA-134) Extend CasCopier to support multiple views

Posted by "Adam Lally (JIRA)" <ui...@incubator.apache.org>.
     [ http://issues.apache.org/jira/browse/UIMA-134?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Work on UIMA-134 started by Adam Lally.

> Extend CasCopier to support multiple views
> ------------------------------------------
>
>                 Key: UIMA-134
>                 URL: http://issues.apache.org/jira/browse/UIMA-134
>             Project: UIMA
>          Issue Type: Improvement
>          Components: Core Java Framework
>            Reporter: Adam Lally
>         Assigned To: Adam Lally
>            Priority: Minor
>
> The CasCopier utility class should support multiple views/Sofas.
> 1) There should be a way to copy multiple views in the source CAS, each to its own view in the target CAS, while keeping a "memory" of copied FS so duplicates are not created.
> 2) References to Sofas need to be preserved in the target CAS.  If we copy a source FS referencing a Sofa with SofaID "Foo" then this should result in a reference to the Sofa with the same SofaID in the target CAS.  If that Sofa does not exist, we can either create it or throw an exception (probably this should be determined by an agument to the method call).

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: http://issues.apache.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira

        

[jira] Resolved: (UIMA-134) Extend CasCopier to support multiple views

Posted by "Adam Lally (JIRA)" <ui...@incubator.apache.org>.
     [ https://issues.apache.org/jira/browse/UIMA-134?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Adam Lally resolved UIMA-134.
-----------------------------

       Resolution: Fixed
    Fix Version/s: 2.1
         Assignee: Eddie Epstein  (was: Adam Lally)

Fixed.  CasCopier should support multiple views now.  Assigning to Eddie for review.

> Extend CasCopier to support multiple views
> ------------------------------------------
>
>                 Key: UIMA-134
>                 URL: https://issues.apache.org/jira/browse/UIMA-134
>             Project: UIMA
>          Issue Type: Improvement
>          Components: Core Java Framework
>            Reporter: Adam Lally
>         Assigned To: Eddie Epstein
>            Priority: Minor
>             Fix For: 2.1
>
>
> The CasCopier utility class should support multiple views/Sofas.
> 1) There should be a way to copy multiple views in the source CAS, each to its own view in the target CAS, while keeping a "memory" of copied FS so duplicates are not created.
> 2) References to Sofas need to be preserved in the target CAS.  If we copy a source FS referencing a Sofa with SofaID "Foo" then this should result in a reference to the Sofa with the same SofaID in the target CAS.  If that Sofa does not exist, we can either create it or throw an exception (probably this should be determined by an agument to the method call).

-- 
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