Uploaded image for project: 'Red Hat Fuse'
  1. Red Hat Fuse
  2. ENTESB-15689

Fuse 7.9 should use Undertow 2.0 whether or not it's aligned to EAP 7.4

    XMLWordPrintable

Details

    • Task
    • Resolution: Unresolved
    • Major
    • None
    • None
    • None
    • None
    • False
    • False
    • % %
    • Undefined

    Description

      EAP 7.4 uses Undertow 2.2.x. Since UNDERTOW-1684, Undertow does not support OSGi at all.
      Fuse-Karaf flavor of Fuse 7 product is OSGi based platform and proper OSGi bundle manifests are crucial to it's operation.

      Whether or not Fuse 7.9 will align to EAP 7.4, Fuse-Karaf part of entire product should continue to use supported version of Undertow 2.0.x.

      It'd be no problem for me to bring back OSGi support to Undertow 2.1+ - especially because I see no linked document that'd justify such removal.
      I have no problems with WFLY-1638 which concerns "JBoss OSGi" in general, but Undertow component itself being used not only in EAP/Wildfly should keep OSGi support - especially because Fuse 7 made such critical decision to switch from Jetty to Undertow.

      /cc: acunning@redhat.com, janstey@redhat.com, gmalinko, drieden@redhat.com, garygaughan, yfang@redhat.com.

      Attachments

        Issue Links

          is incorporated by

          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) ENTESB-15356 Upgrade to EAP-7.4.0.CD21

          • 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.
          • Done
          is related to

          Component Upgrade - A task tracking an update to a bundled component or revision of component upstream of the project. WFCORE-5329 Upgrade Undertow to 2.2.5.Final

          • Critical - To be worked on immediately following BLOCKER issues.
          • Closed
          relates to

          Task - Represents a small unit of work that is not end-user facing. UNDERTOW-1852 Add OSGi support

          • Critical - To be worked on immediately following BLOCKER issues.
          • Resolved

          Task - Represents a small unit of work that is not end-user facing. UNDERTOW-1684 Remove OSGi support

          • 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

          Activity

            People

              Unassigned Unassigned
              ggrzybek Grzegorz Grzybek
              Votes:
              0 Vote for this issue
              Watchers:
              3 Start watching this issue

              Dates

                Created:
                Updated: