Skip to content
Ilya Muromtsev edited this page Jun 16, 2026 · 2 revisions

Usage

Everyday workflows with Explyt Spring. New to the plugin? Do the Installation Guide first.

Three core workflows

  1. Understand beans — open Explyt SpringLink Explyt Spring Boot Project From RunConfigurationLoad Beans → open Bean Analyzer.
  2. Navigate APIs — open Explyt Endpoints → filter routes/listeners → jump to handler code.
  3. Test HTTP — run Spring Web methods in Swagger UI, or execute .http/.rest requests.

Tool windows

Explyt Spring (beans & context)

Open the Explyt Spring tool window (right sidebar). Link a Spring Boot run configuration, then click Load Beans / Refresh. Browse contexts, beans, aspects, inactive beans, and library beans. See Native Context Mode for how the bean data is built.

  • Bean Analyzer — click the toolbar action to open the Dependency Analyzer view for the current context and navigate between related beans.

Explyt Endpoints

Open Explyt Endpoints to browse and navigate Spring MVC/WebFlux endpoints, router functions, JAX-RS endpoints, and message-broker listeners (Kafka/RabbitMQ). Filter and jump straight to handler code.

Built-in HTTP client

Two ways to test requests:

Inspections & quick fixes

The plugin highlights potential issues in your Spring application. Press Alt+Enter on a highlight to see Spring-aware quick fixes.

Code completion & navigation

Improved completion across properties files and annotations; navigate easily between beans, configurations, and endpoints. Gutter icons mark Spring components, endpoints, and scheduled tasks — click to jump to related code.

Code generation

From Code → Generate (Alt+Insert / ⌘N): Spring Web Method from URL/cURL, standalone java.net.http.HttpClient method, JPA equals/hashCode, OpenAPI generation, and Properties ↔ YAML. Full list with demos: Code Generations.

Productivity extras

  • Beans in Search Everywhere — press Shift twice → Beans tab → jump to any bean by name.
  • Mark directory as Spring Application Property Folder — Project View → right-click a directory → Mark Directory asSpring Application Property Folder to enable completion/validation in non-standard config locations.
  • Inlay hints & Code Vision@Profile expression results inline, and runtime property values during Explyt debug sessions (see Spring Debugger).
  • Kotlin support — specialized inspections for Kotlin Spring applications (see Features).

See also: Features · Native Context Mode · MCP Tools

Clone this wiki locally