#13 Separate Interface/Implementation Jars

closed-fixed
None
5
2003-07-20
2003-06-14
No

I was just wondering if it would be possible to
separate out implementation and interface classes
in the JMX distribution. Currently mx4j-jmx.jar
includes javax.management.* classes aswell as
mx4j specific classes. What I would like to do is have
a separate jar "jmx.jar" that just includes
javax.management.* classes.

The reason for this is I want to have jmx.jar in a
base classloader and mx4j-jmx.jar in a child
classloader. The reason for this is that it makes it
more difficult for one application to bind to mx4j
specific implementation of jmx by binding to JMX
directly.

It also makes it more difficult for code to futz with
MX4J internals unless they were specifically allowed
to do it (by being given access to specified
classloader).

Discussion

  • Marcel Offermans

    Logged In: YES
    user_id=265398

    I would like this too, since I am trying to separate interface and
    implementation of a JMX framework within OSGi. Apart from the
    code being in one single JAR at the moment, there are also a
    couple of references from javax.management classes to mx4j
    classes which is something that should be avoided if possible
    (especially since most references are only to implement mx4j
    specific logging within those classes).

     
  • Simone Bordet

    Simone Bordet - 2003-07-20
    • assigned_to: nobody --> biorn_steedom
    • summary: Seprate Interface/Implementation Jars --> Separate Interface/Implementation Jars
    • status: open --> closed-fixed
     
  • Simone Bordet

    Simone Bordet - 2003-07-20

    Logged In: YES
    user_id=128193

    This RFE is more or less complete in the CVS main trunk build
    system.

    Of course at the first release of MX4J 1.2-alpha, those
    interested can comment if it is good enough.

    For now I am closing it as fixed.

    Simon

     

Log in to post a comment.

Get latest updates about Open Source Projects, Conferences and News.

Sign up for the SourceForge newsletter:

JavaScript is required for this form.





No, thanks