Skip to main content

Quickstart

This walkthrough takes you from a freshly installed plugin to real bean data, navigable endpoints, and an executed HTTP request. It assumes you already installed Explyt Spring and have a Spring Boot project open.

1. Load the real bean model​

Everything else in the plugin gets more accurate once the bean model is loaded.

  1. Open the Explyt Spring tool window (right sidebar).
  2. Click Link Explyt Spring Boot Project From RunConfiguration and pick the run configuration that starts your application.

That single step does the work: the plugin compiles your project and performs a lightweight load of the application to read actual bean metadata. It does not fully start your app — no server port is bound and no request traffic is served.

When it finishes, the tool window shows your contexts and beans. Double-click any bean to jump to its declaration.

If loading fails, build the project first (Build → Build Project) and try again. Native context mode supports Spring Boot 2.4 and newer out of the box — see Troubleshooting for older versions.

What you get from this step: conditional beans, profile-activated beans, factory beans, and beans from your dependencies all resolve correctly, so autowiring inspections stop producing false warnings. See Native Context Mode.

2. Browse your endpoints​

Open the Explyt Endpoints tool window. It lists, in one place:

  • Spring MVC and WebFlux endpoints
  • Router functions, including Kotlin coRouter
  • Message broker listeners, such as @KafkaListener and @RabbitListener
  • JAX-RS resources in Quarkus projects

Filter the list and click through to the handler code. See Tool windows.

3. Find a bean fast​

Press Shift twice to open Search Everywhere and switch to the Beans tab. Type a bean name to jump straight to its declaration.

To explore how beans depend on one another, open Bean Analyzer from the Explyt Spring tool window toolbar.

4. Run an HTTP request​

You have two options; pick the one that matches how you work.

Option A — Swagger UI from Spring annotations. Write a method with a standard Spring Web annotation and an absolute URL:

@GetMapping("https://api.openweathermap.org/data/2.5/weather")
public String getWeather() {
    // The implementation does not matter — the annotation defines the request
}

A Run icon appears in the gutter. Click it to generate an OpenAPI definition and open Swagger UI inside the IDE, where you can fill in parameters, execute, inspect the response, and copy the generated cURL. See Swagger UI client.

Option B — a .http file. Create a file with the .http extension and write a request:

### Get a sample
GET https://httpbin.org/anything
Accept: application/json

Click the ▶️ Run icon next to the request. This needs a runner configured once — see .http and .rest files.

5. Act on inspections​

The plugin highlights Spring-specific problems as you type: missing or ambiguous autowiring candidates, invalid @ConfigurationProperties prefixes, duplicate endpoint paths, AOP self-invocation, unused property keys, and more.

Press Alt+Enter on any highlight to see the available quick fixes. The full catalogue is in Inspections.

6. Generate boilerplate​

Press Alt+Insert (⌘N on macOS) in a Java or Kotlin file to reach the Spring-aware generators: a Spring Web method from a URL or cURL command, a standalone HttpClient method, proxy-safe JPA equals/hashCode, and Properties ↔ YAML conversion. See Code generation.

Next steps​