Mailing-List: contact dev-help@batchee.incubator.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@batchee.incubator.apache.org
Date: Tue, 6 May 2014 08:32:15 +0000 (UTC)
From: "Romain Manni-Bucau (JIRA)" <jira@apache.org>
To: dev@batchee.incubator.apache.org
Message-ID: <JIRA.12712351.1399310137130.235073.1399365135708@arcas>
In-Reply-To: <JIRA.12712351.1399310137130@arcas>
References: <JIRA.12712351.1399310137130@arcas>
Subject: [jira] [Commented] (BATCHEE-36) Befor- and
 AfterJob(Step)ScopeListener
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit


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

Romain Manni-Bucau commented on BATCHEE-36:
-------------------------------------------

well, to be honest I think we can keep it as it is today and add a CDI extension checking if JobScoped/StepScoped are used. Then when we start the batch we can just add the listeners automatically if needed without any config.

When I wrote this part the main issue was the config. I added something simple but it is clear having to configure it manually is not the final solution.


> Befor- and AfterJob(Step)ScopeListener
> --------------------------------------
>
>                 Key: BATCHEE-36
>                 URL: https://issues.apache.org/jira/browse/BATCHEE-36
>             Project: BatchEE
>          Issue Type: Improvement
>          Components: batchee-extensions
>    Affects Versions: 0.2-incubating
>            Reporter: Reinhard Sandtner
>            Priority: Minor
>
> why do we provide an AfterJob(Step)ScopeListener and a BeforeJob(Step)ScopeListener?
> Isn't it enough to have only one JobScopeListener and StepScopeListener which implements both methods?
> {code}
> public void before(){...}
> public void after(){...}
> {code}


--
This message was sent by Atlassian JIRA
(v6.2#6252)