Avalon Phoenix
  1. Avalon Phoenix
  2. PNIX-26

Separate JMX Interfaces and Implemention in MX4J

    Details

    • Type: Improvement Improvement
    • Status: Open
    • Priority: Critical Critical
    • Resolution: Unresolved
    • Affects Version/s: 4.1
    • Fix Version/s: None
    • Component/s: System Manager (JMX)
    • Labels:
      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.

        Issue Links

          Activity

          Hide
          Peter Donald added a comment -

          Whats the status of this?

          Show
          Peter Donald added a comment - Whats the status of this?

            People

            • Assignee:
              Paul Hammant
              Reporter:
              Peter Donald
            • Votes:
              0 Vote for this issue
              Watchers:
              0 Start watching this issue

              Dates

              • Created:
                Updated:

                Development