[
https://issues.jboss.org/browse/WFLY-7210?page=com.atlassian.jira.plugin....
]
Lin Gao commented on WFLY-7210:
-------------------------------
[~ggam] I am really sorry for the late reply. :-)
What was concerned when implementing WFLY-7024 without more level of sub resources is that
it may produce too much resources and sub-resources in case of large deployments in
memory. And the REST endpoints information will probably be parsed during deployment time,
which will potentially impact the deployment time.
Current design is that each root REST resource is added during deployment by
{{JaxrsScanningProcessor}} without further analyzing inside of the ResourceClass. The
{{:read-resource()}} operation will read the information in {{ResourceMethodRegistry}}
exposed by {{HttpServletDispatcher}} at run-time.
Is it possible that the web console can parse the data for the jaxrs subsystem to
customize the UI as we want?
[~mkopecky] [~harald.pehl] WDYT?
Expose JAX-RS resources as children of the subsystem
----------------------------------------------------
Key: WFLY-7210
URL:
https://issues.jboss.org/browse/WFLY-7210
Project: WildFly
Issue Type: Feature Request
Components: REST
Affects Versions: 10.1.0.Final
Reporter: Guillermo González de Agüero
Assignee: Lin Gao
Attachments: after-wfly7024.png, hal-jaxrs.png
Servlets, EJBs, WebSockets, JPA, etc expose its components as children of the subsystem
in the management API. For example to list the stateless EJBs of a deployment:
[standalone@localhost:9990 /]
/deployment=cdivsejb.war/subsystem=ejb3:read-children-resources(child-type=stateless-session-bean)
This makes it specially easy to navigate trough the web console (attached screenshot).
To read JAX-RS resources, the command would be:
[standalone@localhost:9990 /] /deployment=cdivsejb.war/subsystem=jaxrs:show-resources()
I propose to make deprecate the show-resources operation and create a new
"resources" child, containing the Rest resources.
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)