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

Posted to dev@batchee.apache.org by "Mark Struberg (JIRA)" <ji...@apache.org> on 2014/05/05 13:45:16 UTC

[jira] [Updated] (BATCHEE-35) add a @PartitionScoped CDI scope

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

Mark Struberg updated BATCHEE-35:
---------------------------------

    Summary: add a @PartitionScoped CDI scope  (was: add a CDI scope which spans a split execution)

> add a @PartitionScoped CDI scope
> --------------------------------
>
>                 Key: BATCHEE-35
>                 URL: https://issues.apache.org/jira/browse/BATCHEE-35
>             Project: BatchEE
>          Issue Type: New Feature
>          Components: batchee-extensions
>    Affects Versions: 0.2-incubating
>            Reporter: Mark Struberg
>
> We have @StepScoped, @JobScoped and from CDI itself we have @RequestScoped.
> If a Step gets executed in form of a Split, then we have multiple Threads running the same Step. How do we account for that? A @StepScoped is too 'wide'.
> A @RequestScoped could probably work, but is there any chance that multiple steps use the same thread without exiting them between two steps? 



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