Uploaded image for project: 'JBoss Metadata'
  1. JBoss Metadata
  2. JBMETA-426

Add support for the EE 10 schemas handled by JBoss Metadata

    XMLWordPrintable

Details

    • Feature Request
    • Resolution: Done
    • Major
    • 15.1.0.Final
    • None
    • client, common
    • None
    • False
    • False
    • 0
    • 0% 0%
    • Untriaged

    Description

      The new schemas are listed at https://jakarta.ee/xml/ns/jakartaee/#10

      Attachments

        Issue Links

          is related to

          Task - Represents a small unit of work that is not end-user facing. JBMETA-427 Add support for draft versions of Common, Application, Application Client and declared permissions Jakarta EE 10 schemas

          • 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. JBMETA-434 Add support for Final versions of Common, Application, Application Client and declared permissions Jakarta EE 10 schemas

          • 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) JBMETA-431 Add support for new concurrency elements in the EE 10 xsds

          • 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) JBMETA-432 Add support for Jakarta EE Web Service 2.0 Metadata

          • 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) JBMETA-433 Add support for Jakarta Faces schema metadata

          • 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) JBMETA-435 Add support for Jakarta Enterprise Beans Jar 4.0 Schema metadata

          • 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) JBMETA-436 Add support for Jakarta Server Pages 3.1 Taglibrary metadata

          • 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

              yborgess1@redhat.com Yeray Borges Santana
              bstansbe@redhat.com Brian Stansberry
              Votes:
              0 Vote for this issue
              Watchers:
              3 Start watching this issue

              Dates

                Created:
                Updated:
                Resolved: