Spring Framework 7 introduced native API versioning, eliminating the need to duplicate controller classes per version. This adds a new enterprise pattern demonstrating the before/after.

Changes

• content/enterprise/spring-api-versioning.json — new pattern (ID 110) contrasting manual URL-path versioning (separate V1/V2 controller classes) against Spring Framework 7's version attribute on @GetMapping with centralized configureApiVersioning() strategy
• content/enterprise/jdbc-resultset-vs-jpa-criteria.json — updated next pointer to enterprise/spring-api-versioning to maintain navigation chain

Example

Before — duplicated controller per version:

@RestController @RequestMapping("/api/v1/products")
public class ProductControllerV1 { ... }

@RestController @RequestMapping("/api/v2/products")
public class ProductControllerV2 { ... }

After — single controller, version per method:

@Configuration
public class WebConfig implements WebMvcConfigurer {
    @Override
    public void configureApiVersioning(ApiVersionConfigurer config) {
        config.useRequestHeader("X-API-Version");
    }
}

@RestController @RequestMapping("/api/products")
public class ProductController {
    @GetMapping(value = "/{id}", version = "1")
    public ProductDtoV1 getV1(@PathVariable Long id) { ... }

    @GetMapping(value = "/{id}", version = "2")
    public ProductDtoV2 getV2(@PathVariable Long id) { ... }
}

• Fixes Spring Framework 7 API Versioning #62

✨ Let Copilot coding agent set things up for you — coding agent works faster and does higher quality work when set up for your repo.