Skip to content

Commit 73bd082

Browse files
author
Mikhail Polivakha
committed
Polishing: Clarified documentation about Endpoint Extensions
Signed-off-by: mipo256 <[email protected]> Signed-off-by: Mikhail Polivakha <[email protected]>
1 parent d4534eb commit 73bd082

File tree

1 file changed

+1
-1
lines changed
  • documentation/spring-boot-docs/src/docs/antora/modules/reference/pages/actuator

1 file changed

+1
-1
lines changed

documentation/spring-boot-docs/src/docs/antora/modules/reference/pages/actuator/endpoints.adoc

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -399,7 +399,7 @@ These endpoints are restricted to their respective technologies.
399399
For example, javadoc:org.springframework.boot.actuate.endpoint.web.annotation.WebEndpoint[format=annotation] is exposed only over HTTP and not over JMX.
400400

401401
You can write technology-specific extensions by using javadoc:org.springframework.boot.actuate.endpoint.web.annotation.EndpointWebExtension[format=annotation] and javadoc:org.springframework.boot.actuate.endpoint.jmx.annotation.EndpointJmxExtension[format=annotation].
402-
These annotations let you provide technology-specific operations to augment an existing endpoint.
402+
These annotations let you provide technology-specific operations to augment an existing endpoint. An endpoint may have at most one extension of each type.
403403

404404
Finally, if you need access to web-framework-specific functionality, you can implement servlet or Spring javadoc:org.springframework.stereotype.Controller[format=annotation] and javadoc:org.springframework.web.bind.annotation.RestController[format=annotation] endpoints at the cost of them not being available over JMX or when using a different web framework.
405405

0 commit comments

Comments
 (0)