You are viewing a plain text version of this content. The canonical link for it is here.

Posted to dev@oozie.apache.org by "Andras Piros (JIRA)" <ji...@apache.org> on 2017/11/16 16:15:00 UTC

[jira] [Updated] (OOZIE-3131) Cut out the creation of AppSubmissionContext from JavaActionExecutor

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

Andras Piros updated OOZIE-3131:
--------------------------------
    Issue Type: Sub-task  (was: Bug)
        Parent: OOZIE-2889

> Cut out the creation of AppSubmissionContext from JavaActionExecutor
> --------------------------------------------------------------------
>
>                 Key: OOZIE-3131
>                 URL: https://issues.apache.org/jira/browse/OOZIE-3131
>             Project: Oozie
>          Issue Type: Sub-task
>            Reporter: Peter Cseh
>
> JavaActionExecutor is huge and a lot of it is createAppSubmissionContext and it's child-functions. This could be pulled out to a AppContextFactory or something similar, which could increase testability of this area greatly as we could write assertions against the AppContext itself. Right now it's nearly impossible to assert what's going inside the AppContext.



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)