I second that. As most JAX-RS stakeholders are MP committers, I do not see a majority for an additional JAX-RS-only solution. What we could do is to make the MP API mandatory to JAX-RS 3.x and define a set of default properties that all existing implementations can provide already.
-Markus
From: jaxrs-dev-bounces@xxxxxxxxxxx [mailto:jaxrs-dev-bounces@xxxxxxxxxxx] On Behalf Of Christian Kaltepoth
Sent: Freitag, 4. Januar 2019 07:30
To: jaxrs developer discussions
Subject: Re: [jaxrs-dev] Monitoring Statistics
I don't think that JAX-RS should build something JAX-RS specific for this. Instead, JAX-RS should integrate with a monitoring mechanism defined as part of the Jakarta EE platform. MicroProfile Metrics would be a good candidate, but it is not part of the Jakarta EE platform (yet).
My suggestion would be to add a feature that allows developers to annotate their resource classes and resource methods with @MStatistics("URI") annotation where the URI is a relative URI to the resource's URI and would correspond to the resources statistics after being invoked using a browser (or any other client type).
example:
@MStatistics("stats")@Path("resource")public class MyResource
{ @GET
public String getResource()
{ return "Hello World";
}
}
then the statistics would be available at URI: http://{host}:{port}/resource/stats_______________________________________________
jaxrs-dev mailing list
jaxrs-dev@xxxxxxxxxxx
To change your delivery options, retrieve your password, or unsubscribe from this list, visit
https://www.eclipse.org/mailman/listinfo/jaxrs-dev
--
