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

WildFly server based on Jakarta EE API should communicate successfully with previous versions of the server based on Java EE

    XMLWordPrintable

Details

    • Task
    • Resolution: Done
    • Major
    • 27.0.0.Beta1, 27.0.0.Final
    • None
    • None
    • None
    • ---
    • ---

    Attachments

      Issue Links

        depends on

        Component Upgrade - A task tracking an update to a bundled component or revision of component upstream of the project. WFLY-17033 Upgrade WildFly Naming Client to 1.0.16.Final

        • 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

        Component Upgrade - A task tracking an update to a bundled component or revision of component upstream of the project. WFLY-17034 Upgrade WildFly HTTP Client to 1.1.14.Final

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

        Task - Represents a small unit of work that is not end-user facing. EJBCLIENT-419 Adapt jboss-ejb-client to work correctly in EAP7<->EAP8 invocation scenarios

        • 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

        Task - Represents a small unit of work that is not end-user facing. JBMAR-238 Provide support for jakarta<->javax transformation in invocations between servers implementing different specification version

        • 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

        Task - Represents a small unit of work that is not end-user facing. WEJBHTTP-79 Adapt wildfly-http-client to work correctly in EAP7<->EAP8 invocation scenarios

        • 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

        Task - Represents a small unit of work that is not end-user facing. WFNC-70 Adapt wildfly-naming-client to work correctly in EAP7<->EAP8 invocation scenarios

        • 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

        Component Upgrade - A task tracking an update to a bundled component or revision of component upstream of the project. WFCORE-5951 Upgrade JBoss Marshalling to 2.1.0.Final

        • 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

        Component Upgrade - A task tracking an update to a bundled component or revision of component upstream of the project. WFLY-17035 Upgrade jboss-ejb-client from 4.0.45.Final to 4.0.47.Final

        • 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

        Activity

          People

            flaviarnn Flavia Rainone
            tadamski@redhat.com Tomasz Adamski
            Votes:
            0 Vote for this issue
            Watchers:
            4 Start watching this issue

            Dates

              Created:
              Updated:
              Resolved: