loom

Separate JMX Interfaces and Implemention in MX4J

Details

  • Type: Improvement Improvement
  • Status: Closed Closed
  • Priority: Critical Critical
  • Resolution: Won't Fix
  • Affects Version/s: None
  • Fix Version/s: None
  • Component/s: None
  • Labels:
    None
  • Number of attachments :
    0

Description

Need to ask the MX4j folks to separate out the API and the implementation into separate jars for their next release. Ideally

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.

Activity

Hide
Permalink
Peter Donald added a comment -

Unfortunately this is not possible as some of the specification classes include MX4J specific classes. It may also not be a smart idea given that as of JDK1.5 the JMX classes will be included in system classpath.

Show
Peter Donald added a comment - Unfortunately this is not possible as some of the specification classes include MX4J specific classes. It may also not be a smart idea given that as of JDK1.5 the JMX classes will be included in system classpath.

People

  • Assignee:
    Unassigned
    Reporter:
    Mauro Talevi
Vote (0)
Watch (0)

Dates

  • Created:
    Updated:
    Resolved: