Yes. Jolokia was considered and is listed as an alternative in the JEP.
On Wednesday 06 September 2017 10:21 AM, Kirk Pepperdine wrote:
Hi, Have you run into this project? https://jolokia.org. Unfortunately it’s not exactly a drop in replacement for the standard RMI based JMX connector but it’s not far off. Kind regards, KirkOn Sep 5, 2017, at 6:30 PM, Erik Gahlin [hidden email] wrote: Hi Harsha, Looping in jmx-dev.byte, short, int, float, doubleShould long be included there as well?The REST adapter will come with a simple and lightweight JSON parser.Is this an internal parser or will it be exposed as an API? If so, how does it relate to JEP 198: Light-Weight JSON API? http://openjdk.java.net/jeps/198 Will com.sun.net.httpserver.HttpServer be used to serve the requests? Thanks ErikHi All, Please review the JEP for REST APIs for JMX : https://bugs.openjdk.java.net/browse/JDK-8171311 The JEP aims at providing RESTful web interfaces to MBeans. Access to MBeans registered in a MBeanServer running inside a JVM requires a Java client. Language-agnostic access to MBeans will require spawning a Java client which can be cumbersome. The proposed JEP allows MBeans to be accessed in a language/platform-independent, ubiquitous and seamless manner. Thanks -Harsha
Would one at least consider adopting the same URL paths and payloads as Jolokia? This could make life a lot easier for third party tools that connect to it.
In my opinion, the interfaces exposed by current JEP are lot
closer to REST style than the interfaces exposed by Jolokia.
For instance, HTTP GET by default should be used to read resources, but it is made part of URL in Jolokia interfaces.
<base-url>/read/<mbean name>/<attribute name>/<inner path>
I would wait on opinions from more people before considering changing the current interfaces.
On Wednesday 06 September 2017 11:40 AM, Martin Skarsaune wrote:
On Monday 11 September 2017 07:14 PM, Erik Gahlin wrote:
Agreed. That will always be the first priority. That is the reason HTTP GET interfaces will not be changed. I am undecided if the POST payloads need to be changed (without compromising the REST design principles) to increase adoption of this feature.
Yes. There is an enhancement request to add the -Xmanagemet:* syntatic sugar for -Dcom.sun.management.jmxremote.* flags. REST adapter will use one of the above flags though I haven't thought of the exact name for it yet. I will update the JEP with the details of the flag shortly.
Notifications will not be supported in this JEP.
Notifications can be added without modifying the current design too much. If required, it will be worked upon via an enhancement request.
|Free forum by Nabble||Edit this page|