Uploaded image for project: 'WildFly'
  1. WildFly
  2. WFLY-16930

Batch subsystem should maintain its own cache of services

    XMLWordPrintable

Details

    • Enhancement
    • Resolution: Unresolved
    • Major
    • None
    • None
    • Batch
    • None
    • ---
    • ---

    Description

      Batch subsystem currently uses org.jboss.msc.service.ServiceController#getService to retrieve services. For instance, 

      BatchSubsystemDefinition and JobOperationStepHandler

      https://github.com/wildfly/wildfly/blob/main/batch-jberet/src/main/java/org/wildfly/extension/batch/jberet/deployment/JobOperationStepHandler.java#L72

      This method has been deprecated, with no direct replacement:

          /**
     * Get the service.
     *
     * @return the service
     * @throws IllegalStateException if the service is not available (i.e. it is not up)
     * @deprecated this method will be removed in a future release
     */
    @Deprecated
    Service<S> getService() throws IllegalStateException;

      In the chat discussion, it's recommended for each subsystem to maintain its own cache of desired services, similar to clustering in this PR.

      Attachments

        Issue Links

          is incorporated by

          Sub-task - The sub-task of the issue WFLY-16850 batch subsystem code standardization

          • Major - To be worked after higher priority work items are addressed. When the severity is high and the effort to change it is low to moderate, this term is chosen. Issues in this category likely have an existing workaround but implementation or execution may be non-trivial.
          • Open
          relates to

          Task - Represents a small unit of work that is not end-user facing. WFLY-16984 Rewrite batch subsystem to use new MSC values API

          • Major - To be worked after higher priority work items are addressed. When the severity is high and the effort to change it is low to moderate, this term is chosen. Issues in this category likely have an existing workaround but implementation or execution may be non-trivial.
          • Closed

          Enhancement - An enhancement to or refactoring of existing functionality that is not configurable by an end user (typically a change made by an internal team that affects users) WFLY-16936 Migrate to msc 2 api with consumer- and supplier-based service

          • Major - To be worked after higher priority work items are addressed. When the severity is high and the effort to change it is low to moderate, this term is chosen. Issues in this category likely have an existing workaround but implementation or execution may be non-trivial.
          • Open

          Activity

            People

              weinanli Weinan Li
              cfang@redhat.com Cheng Fang
              Votes:
              0 Vote for this issue
              Watchers:
              2 Start watching this issue

              Dates

                Created:
                Updated: