Uploaded image for project: 'jBPM'
  1. jBPM
  2. JBPM-6243

Run workbench console using standalone controller

    XMLWordPrintable

Details

    • Feature Request
    • Resolution: Done
    • Critical
    • 7.7.0.Final
    • None
    • Console
    • None
    • NEW
    • NEW
    • 0
    • 0% 0%
    • 2017 Week 30-31, 2017 Week 40-41-42, 2017 Week 43-44, 2017 Week 45-46, 2017 Week 47-48, 2017 Week 49-50, 2017 Week 51-52, 2018 Week 01-02, 2018 Week 03-04, 2018 Week 05-06

    Description

      Instead of relying on it own, embedded controller, the console should be able to run using a standalone controller.

      Attachments

        Issue Links

          is related to

          Task - Represents a small unit of work that is not end-user facing. JBPM-6627 Extend tests for Kie Server Controller Integration tests

          • 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) JBPM-6792 Allow loading controller password using Keystore

          • 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.
          • Resolved

          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) JBPM-7360 Extend Kie Server Controller client REST endpoints

          • 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.
          • Resolved
          relates to

          Epic - Issue type for a big user story that needs to be broken down into a grouping of stories, tasks, and other issues that contribute to the delivery of the Epic. Created by Jira Software - do not edit or delete. JBPM-6148 Create console distribution including only runtime views

          • Blocker - To be worked above all other priorities. This term is chosen when the severity of the issue is very high, has no workaround, or the effort for the change is comparatively low. Issues that may be very publicly visible and could generate significant media attention may also drive a higher priority.
          • Resolved

          Activity

            People

              cnicolai@redhat.com Cristiano Nicolai
              cnicolai@redhat.com Cristiano Nicolai
              Votes:
              0 Vote for this issue
              Watchers:
              7 Start watching this issue

              Dates

                Created:
                Updated:
                Resolved: