You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@daffodil.apache.org by "Dave Thompson (Jira)" <ji...@apache.org> on 2022/08/17 15:09:00 UTC

[jira] [Closed] (DAFFODIL-2723) Change DataProcessor.copy() method to public

     [ https://issues.apache.org/jira/browse/DAFFODIL-2723?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Dave Thompson closed DAFFODIL-2723.
-----------------------------------

Verified the specified commit (commit da0a424f9e35164487d3218880a261c9169aa7ba) is included in the latest pull from the daffodil repository.

Verified, via review, changes identified in commit comment were implemented.

Verified the all affected daffodil subproject sbt test suite execute successfully.

> Change DataProcessor.copy() method to public
> --------------------------------------------
>
>                 Key: DAFFODIL-2723
>                 URL: https://issues.apache.org/jira/browse/DAFFODIL-2723
>             Project: Daffodil
>          Issue Type: New Feature
>          Components: Back End
>    Affects Versions: 3.3.0
>            Reporter: Mike Beckerle
>            Assignee: Mike Beckerle
>            Priority: Major
>             Fix For: 3.4.0
>
>
> I need to copy a DataProcessor in order to avoid reloading it (which takes 10+ seconds on a very large schema project.)
> For some reason the copy() method on DataProcessor is private. 
> I can't think of a good reason it *needs* to be private, other than fewer public methods is better. But I really need this in a test rig I've built for a schema project. I need to create a DP instance, and then copy it so that I can have both a regular DP and one with Trace/Debug and have both initialized but only restoring the DP from a file *once.* 
> This test rig is not using SAPI, as I've found I have other reasons to use internal interfaces of Daffodil, like using a variety of access to Infoset Inputters/Outputters.



--
This message was sent by Atlassian Jira
(v8.20.10#820010)