-
Enhancement
-
Resolution: Done
-
Major
-
7.0.0.ER6, 7.2.0.GA
-
2
-
-
-
-
-
-
+
-
EAP DOC Sprint 7:Mar29 - Apr 9
Guide: Developing Web Services Applications
RESTEasy - RegistryStatsResource end-point is not described in documentation.
- You can get information about application's REST end-points by RegistryStatsResource.
- RegistryStatsResource needs to be registered as resource in RESTEasy, for example by this context parameter in web.xml:
<context-param> <param-name>resteasy.resources</param-name> <param-value>org.jboss.resteasy.plugins.stats.RegistryStatsResource</param-value> </context-param>
- information about application REST end-points are available on:
http://${hostname}:${port}/{application_prefix_url}/resteasy/registry - default response format is in XML, but client can require also JSON format
- example of response:
<registry> <resource uriTemplate="/resource"> <delete class="org.jboss.resteasy.test.providers.jaxb.resource.StatsResource" method="delete" invocations="0"/> <head class="org.jboss.resteasy.test.providers.jaxb.resource.StatsResource" method="head" invocations="0"/> </resource> <resource uriTemplate="/locator"> <locator class="org.jboss.resteasy.test.providers.jaxb.resource.StatsResource" method="getLocator"/> </resource> <resource uriTemplate="/resteasy/registry"> <get class="org.jboss.resteasy.plugins.stats.RegistryStatsResource" method="get" invocations="2"> <produces>application/xml</produces> <produces>application/json</produces> </get> </resource> <resource uriTemplate="/entry/{foo:.*}"> <post class="org.jboss.resteasy.test.providers.jaxb.resource.StatsResource" method="post" invocations="0"> <produces>text/xml</produces> <consumes>application/json</consumes> </post> <put class="org.jboss.resteasy.test.providers.jaxb.resource.StatsResource" method="put" invocations="0"> <produces>text/xml</produces> <consumes>application/json</consumes> </put> </resource> </registry>
- this feature is not part of JAX-RS 2.0 specification
- is cloned by
-
JBEAP-17628 [CD-18] RESTEasy - RegistryStatsResource end-point is not described in documentation
-
- Closed
-
