Skip to content

Commit b399eb3

Browse files
author
Mikhail Polivakha
committed
Polishing: Clarified documentation about Endpoint Extensions
Signed-off-by: mipo256 <mikhailpolivakha@email.com>
1 parent d4534eb commit b399eb3

File tree

1 file changed

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

1 file changed

+2
-0
lines changed

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

Lines changed: 2 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -401,6 +401,8 @@ For example, javadoc:org.springframework.boot.actuate.endpoint.web.annotation.We
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].
402402
These annotations let you provide technology-specific operations to augment an existing endpoint.
403403

404+
NOTE: As of now, it is possible to have only a single extension per an individual javadoc:org.springframework.boot.actuate.endpoint.annotation.Endpoint[format=annotation].
405+
404406
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.
405407

406408

0 commit comments

Comments
 (0)