Uploaded image for project: 'Avalon Phoenix'
  1. Avalon Phoenix
  2. PNIX-26

Separate JMX Interfaces and Implemention in MX4J

    XMLWordPrintableJSON

Details

    • Improvement
    • Status: Open
    • Critical
    • Resolution: Unresolved
    • 4.1
    • None
    • System Manager (JMX)
    • None

    Description

      Need to ask the MX4j folks to separate out the API and the implementation into separate jars for their next release. Ideally what I would like to see is a

      jmx-api.jar (contains javax.management.**)
      mx4j-jmx.jar (contains mx4j.**)

      Doing this would enable us to place the jmx-api.jar in the root classloader and thus allows us to safely enable access to management subsystem from within blocks.

      Attachments

        Issue Links

          duplicates

          Improvement - An improvement or enhancement to an existing feature or task. PNIX-17 JMX separation between Impl and Interfaces

          • Major - Major loss of function.
          • Closed

          Activity

            People

              paul Paul Hammant
              pdonald Peter Donald
              Votes:
              0 Vote for this issue
              Watchers:
              0 Start watching this issue

              Dates

                Created:
                Updated: