Petals CDK

Remove uses of ExecutionContext, always use PetalsExecutionContext instead

Details

  • Type: Task Task
  • Status: Resolved Resolved
  • Priority: Major Major
  • Resolution: Fixed
  • Affects Version/s: 5.6.0
  • Fix Version/s: 5.6.1
  • Component/s: None
  • Security Level: Public
  • Description:
    Hide

    In order for PETALSESBCONT-424 to be realised, ExecutionContext is not going to be used anymore.

    Unfortunately, some code in the CDK calls ExecutionContext instead of using the API provided by PetalsExecutionContext (that used ExecutionContext internally in the past and that will replace it with slf4j's MDC).

    This will impacts all the components that want to run on the container 5.0.2+.

    A a side note, it also means that any dependency to jcl-over-slf4j, log4j-over-slf4j, slf4j-jdk14 or slf4j-api will be removed from the components zip (because they are already present in the system classloader, see PETALSDISTRIB-256)

    Show
    In order for PETALSESBCONT-424 to be realised, ExecutionContext is not going to be used anymore. Unfortunately, some code in the CDK calls ExecutionContext instead of using the API provided by PetalsExecutionContext (that used ExecutionContext internally in the past and that will replace it with slf4j's MDC). This will impacts all the components that want to run on the container 5.0.2+. A a side note, it also means that any dependency to jcl-over-slf4j, log4j-over-slf4j, slf4j-jdk14 or slf4j-api will be removed from the components zip (because they are already present in the system classloader, see PETALSDISTRIB-256)
  • Environment:
    -

Issue Links

Activity

Transition Status Change Time Execution Times Last Executer Last Execution Date
New New Open Open
11s
1
Victor NOËL
Tue, 31 May 2016 - 16:52:19 +0200
Open Open In Progress In Progress
4s
1
Victor NOËL
Tue, 31 May 2016 - 16:52:23 +0200
In Progress In Progress Resolved Resolved
18h 29m
1
Victor NOËL
Wed, 1 Jun 2016 - 11:21:28 +0200

People

Dates

  • Created:
    Tue, 31 May 2016 - 16:52:08 +0200
    Updated:
    Wed, 1 Jun 2016 - 11:29:34 +0200
    Resolved:
    Wed, 1 Jun 2016 - 11:21:28 +0200