Uploaded image for project: 'Application Server 3 4 5 and 6'
  1. Application Server 3 4 5 and 6
  2. JBAS-7789

Allow the default jmx name of EJB(2.x) deployments to be deterministic

    XMLWordPrintable

Details

    • Task
    • Resolution: Done
    • Major
    • 6.0.0.M3
    • 6.0.0.M1, 6.0.0.M2
    • Deployers, EJB2
    • None

    Description

      The fix for https://jira.jboss.org/jira/browse/JBPAPP-2419 resulted in the default jmx name of the EJB2 deployment, non-deterministic. Many users depend on this default jmx name to add a dependency between deployments. For example, JBAS-7760 illustrates one such use case. Making the default, jmx name deterministic will allow users to use this in the <depends> element of deployments.

      At the same time, care has to be taken that the original bug reported in JBPAPP-2419 is not reintroduced as part of this change.

      Attachments

        Issue Links

          blocks

          Bug - A problem that impairs or prevents the functions of the product. JBAS-7760 Error when defining dependency between an EAR and its related WAR

          • 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

          Bug - A problem that impairs or prevents the functions of the product. JBPAPP-2419 JBAS-6335 - EjbModule is already installed

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

          Bug - A problem that impairs or prevents the functions of the product. JBPAPP-8070 Allow the default jmx name of EJB(2.x) deployments to be deterministic so ejb can depend on ejb

          • Minor - To be worked after urgent, high, and medium priorities are resolved. This term is chosen when the severity of the issue is low, or the complexity or effort to correct it may be higher, relatively speaking. For low priority issues, known workarounds exist or are not needed due to the trivial effort needed to address the issue.
          • Closed

          Activity

            People

              jaikiran Jaikiran Pai (Inactive)
              jaikiran Jaikiran Pai (Inactive)
              Votes:
              0 Vote for this issue
              Watchers:
              0 Start watching this issue

              Dates

                Created:
                Updated:
                Resolved: