The JavaTMManagement Extension [JMX] defines the way in which resources are instrumented within a management agent based on Java technology, and a certain number of agent-local services based on that instrumentation. JMX Remote API [JSR 160] standardizes a remote access API and protocol to that instrumentation.
The JSR 160 specifications additionally define how JMX Agents can be registered with several well known lookup infrastructures, such as the Service Location Protocol (SLP), JNDI/LDAP, and Jini. Section 6. of the JSR 160 specifications "Binding to Lookup Services", details the conventions to be followed so that a server can be registered and found by clients, without having to share special knowledge between client and server.
This project defines the Jini Entries needed to use the Jini Lookup Service to register and discover JMX Agents as discussed in JSR 160 specifications.
The Open Hub computes statistics on FOSS projects by examining source code and commit history in source code management systems. The source code for this project has been located, but the analysis isn't complete. Feel free to check its progress.
in 2016, 47% of companies did not have formal process in place to track OS code
...
by exploring contributors within projects, you can view details on every commit
they have made to that project
Code analysis has not completed
The Open Hub computes statistics on FOSS projects by examining source code and commit history in source code management systems. The source code for this project has been located, but the analysis isn't complete. Feel free to check its progress.
This site uses cookies to give you the best possible experience.
By using the site, you consent to our use of cookies.
For more information, please see our
Privacy Policy