[jira] [Commented] (DAFFODIL-2242) Remove DaffodilTunables object from DPathCompileInfo and RuntimeData objects.

["Steve Lawrence (Jira)" <ji...@apache.org>]

    [ https://issues.apache.org/jira/browse/DAFFODIL-2242?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16980330#comment-16980330 ] 

Steve Lawrence commented on DAFFODIL-2242:
------------------------------------------

I think there's maybe an argument for serializing tunables. For example, I can imagine setting bunch of tunables on the data processor and then serializing. Upon reloading, I think I might expect that those tunables that I set would keep their values without having to set them all again.

> Remove DaffodilTunables object from DPathCompileInfo and RuntimeData objects.
> -----------------------------------------------------------------------------
>
>                 Key: DAFFODIL-2242
>                 URL: https://issues.apache.org/jira/browse/DAFFODIL-2242
>             Project: Daffodil
>          Issue Type: Improvement
>          Components: Back End, Front End
>    Affects Versions: 2.4.0
>            Reporter: Mike Beckerle
>            Assignee: Mike Beckerle
>            Priority: Major
>             Fix For: 2.5.0
>
>
> Currently the tunables are stored on the DPathCompileInfo objects, which are runtime objects created by the schema compiler.
> This is a mistake. Many tunables mostly can vary at runtime. If at runtime one gets tunables from the RuntimeData by mistake, one will not get the new values. 
> The ones that are needed at schema compile time (e.g., unqualifiedPathStepPolicy)  should be passed and saved separately in the DPathCompileInfo objects and RuntimeData objects that need it. 
> It is possible that DaffodilTunables should not be serializable to prevent this problem. 



--
This message was sent by Atlassian Jira
(v8.3.4#803005)