Uploaded image for project: 'JBoss Enterprise Application Platform 4 and 5'
  1. JBoss Enterprise Application Platform 4 and 5
  2. JBPAPP-10428

Unsigned jbossxts.sar in EAP 5.2.0.ER5

    XMLWordPrintable

Details

    • Not Required
    • NEW

    Description

      JBoss XTS Transactions is a fully supported component of EAP 5.2.x. Its bits are located in docs/examples/transactions/jbossxts.sar file and the issue is that this file is not signed.
      Please, sign content of the jbossxts.sar properly.

      In term of the signing sar is meant singing all jars inside of the sar archive. In previous releases there were some java classes not packed in any jar and this should be fixed by TS dev for the next EAP realese.

      Attachments

        Issue Links

          blocks

          Bug - A problem that impairs or prevents the functions of the product. JBPAPP-10433 Sign JBoss Transaction sar files

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

          Bug - A problem that impairs or prevents the functions of the product. JBPAPP-10384 XTS transactions - failing on deployment - jar signing problem

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

          Bug - A problem that impairs or prevents the functions of the product. JBPAPP-10395 Unsigned jbossts-tools.sar in EAP 5.2.0.ER4

          • 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) JBTM-1342 XTS sar distribution - pack .class files from exploded directory to a jar file

          • 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) JBTM-2104 XTS war distribution within jbossxts.sar - pack .class files from WEB-INF/classes directory to a jar file

          • 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

              huwang@redhat.com Hui Wang
              ochaloup@redhat.com Ondrej Chaloupka (Inactive)
              Votes:
              0 Vote for this issue
              Watchers:
              6 Start watching this issue

              Dates

                Created:
                Updated:
                Resolved: