[prev in list] [next in list] [prev in thread] [next in thread] 

List:       openjdk-serviceability-dev
Subject:    Re: JEP review : JDK-8171311 - REST APIs for JMX
From:       Harsha Wardhana B <harsha.wardhana.b () oracle ! com>
Date:       2017-09-06 5:15:59
Message-ID: ccd8f6ac-9280-61a2-d2f7-505da9619b9a () oracle ! com
[Download RAW message or body]

Hi Kirk,

Yes. Jolokia was considered and is listed as an alternative in the JEP.

  * Jolokia can serve as a viable alternative but can be bulky. We are
    looking for simple and lightweight solution.


-Harsha

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,
> Kirk
> 
> > On Sep 5, 2017, at 6:30 PM, Erik Gahlin <erik.gahlin@oracle.com> wrote:
> > 
> > Hi Harsha,
> > 
> > Looping in jmx-dev.
> > 
> > > byte[], short[], int[], float[], double[]
> > Should 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
> > Erik
> > 
> > > Hi 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
> > > 
> > > 


[Attachment #3 (text/html)]

<html>
  <head>
    <meta http-equiv="Content-Type" content="text/html; charset=UTF-8">
  </head>
  <body>
    Hi Kirk,<br>
    <br>
    Yes. Jolokia was considered and is listed as an alternative in the
    JEP.<br>
    <br>
    <ul style="margin: 10px 0px 0px; color: rgb(51, 51, 51);
      font-family: Arial, sans-serif; font-size: 14px; font-style:
      normal; font-variant-ligatures: normal; font-variant-caps: normal;
      font-weight: normal; letter-spacing: normal; orphans: 2;
      text-align: start; text-indent: 0px; text-transform: none;
      white-space: normal; widows: 2; word-spacing: 0px;
      -webkit-text-stroke-width: 0px; background-color: rgb(255, 255,
      255); text-decoration-style: initial; text-decoration-color:
      initial;">
      <li>Jolokia can serve as a viable alternative but can be bulky. We
        are looking for simple and lightweight solution.</li>
    </ul>
    <br>
    -Harsha<br>
    <br class="Apple-interchange-newline">
    <div class="moz-cite-prefix">On Wednesday 06 September 2017 10:21
      AM, Kirk Pepperdine wrote:<br>
    </div>
    <blockquote type="cite"
      cite="mid:B41B30A1-9EA0-4327-8E19-92A6633F06A7@gmail.com">
      <pre wrap="">Hi,

Have you run into this project? <a class="moz-txt-link-freetext" \
href="https://jolokia.org">https://jolokia.org</a>. Unfortunately it's not exactly a \
drop in replacement for the standard RMI based JMX connector but it's not far off.

Kind regards,
Kirk

</pre>
      <blockquote type="cite">
        <pre wrap="">On Sep 5, 2017, at 6:30 PM, Erik Gahlin <a \
class="moz-txt-link-rfc2396E" \
href="mailto:erik.gahlin@oracle.com">&lt;erik.gahlin@oracle.com&gt;</a> wrote:

Hi Harsha,

Looping in jmx-dev.

</pre>
        <blockquote type="cite">
          <pre wrap="">byte[], short[], int[], float[], double[]
</pre>
        </blockquote>
        <pre wrap="">
Should long[] be included there as well?

</pre>
        <blockquote type="cite">
          <pre wrap="">The REST adapter will come with a simple and lightweight JSON \
parser. </pre>
        </blockquote>
        <pre wrap="">
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?
<a class="moz-txt-link-freetext" \
href="http://openjdk.java.net/jeps/198">http://openjdk.java.net/jeps/198</a>

Will com.sun.net.httpserver.HttpServer be used to serve the requests?

Thanks
Erik

</pre>
        <blockquote type="cite">
          <pre wrap="">Hi All,

Please review the JEP for REST APIs for JMX :
       <a class="moz-txt-link-freetext" \
href="https://bugs.openjdk.java.net/browse/JDK-8171311">https://bugs.openjdk.java.net/browse/JDK-8171311</a>


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


</pre>
        </blockquote>
        <pre wrap="">
</pre>
      </blockquote>
      <pre wrap="">
</pre>
    </blockquote>
    <br>
  </body>
</html>



[prev in list] [next in list] [prev in thread] [next in thread]

Configure | About | News | Add a list | Sponsored by KoreLogic