If only Jersey supports this functionality than there is only small chance to get a generic JAX-RS agreement in short term. Maybe you should first ask CXF and RESTeasy to cover this, and after that come back with a proposal for a generic JAX-RS wrapper? :-) -Markus From: jaxrs-dev-bounces@xxxxxxxxxxx [mailto:jaxrs-dev-bounces@xxxxxxxxxxx] On Behalf Of rawand takna
Sent: Samstag, 5. Januar 2019 06:43
To: jaxrs developer discussions
Subject: Re: [jaxrs-dev] Monitoring Statistics You mean other JAX-RS implementations (CFX, RESTlet, etc.)?
actually no, all my focus is on the jersey, since I can't study the user guides of all the providers (jersey's guide alone is a lot to study) btw, I mistakenly thought that this mailing list is Jersey-specific (not JAX-RS) that's why I talked about the jersey and not JAX-RS in general. Understood. Are you aware of other JAX-RS products besides Jersey which do support monitoring? -Markus A standard API for gathering monitoring statistics would be perfect, but JAX-RS does not define any. All the monitoring statistics mechanisms are available as JERSEY extension modules. that's why I thought that jersey would be able to add a such a feature on top of existing mechanisms already defined by the jersey project. 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 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
-- _______________________________________________
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
_______________________________________________
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
|
