Details

    • Type: New Feature New Feature
    • Status: Closed
    • Priority: Major Major
    • Resolution: Fixed
    • Affects Version/s: 1.0.0.rc1
    • Fix Version/s: 1.1.0
    • Component/s: Core
    • Labels:
      None

      Description

      1) Add an object of type ExecutionContext to JobExecution with a public getter
      2) Persist this automatically in a logical way in the repository (i.e. do some minimum logic to ease the risk of naming collisions with lower-level collaborators)
      3) Retrieve this automatically in a logical way from the repository

      The idea would be to allow inter-step communication (1) while preserving restart logic (2,3).

      I know this has been mentioned and discussed before - just created an issue for it so there's an official record of it and someplace comments can be directed.

        Activity

        Hide
        Robert Kasanicky added a comment -

        Added the createTime property & column and made startTime null until actually started.

        Show
        Robert Kasanicky added a comment - Added the createTime property & column and made startTime null until actually started.
        Hide
        Dave Syer added a comment -

        Is there any reason that the ExecutionContext in JobExecution should not be volatile?

        Show
        Dave Syer added a comment - Is there any reason that the ExecutionContext in JobExecution should not be volatile?
        Hide
        Robert Kasanicky added a comment -

        I'm not sure how some of the properties ended up to be non-volatile - anyway all properties are volatile now.

        Show
        Robert Kasanicky added a comment - I'm not sure how some of the properties ended up to be non-volatile - anyway all properties are volatile now.
        Hide
        Robert Kasanicky added a comment - - edited

        added jobExecutionContextSample job - simple example of inter-step communication

        Show
        Robert Kasanicky added a comment - - edited added jobExecutionContextSample job - simple example of inter-step communication
        Hide
        Dave Syer added a comment -

        Assume closed as resolved and released

        Show
        Dave Syer added a comment - Assume closed as resolved and released

          People

          • Assignee:
            Robert Kasanicky
            Reporter:
            Douglas C. Kaminsky
          • Votes:
            4 Vote for this issue
            Watchers:
            2 Start watching this issue

            Dates

            • Created:
              Updated:
              Resolved:

              Time Tracking

              Estimated:
              Original Estimate - 1d
              1d
              Remaining:
              Remaining Estimate - 1d
              1d
              Logged:
              Time Spent - Not Specified
              Not Specified