Spring 7 migrates from its own org.springframework.lang null annotations to JSpecify, a cross-ecosystem standard. This adds an enterprise pattern demonstrating the contrast.

New pattern: enterprise/spring-null-safety-jspecify

Before (Spring 5/6) — every non-null element requires explicit annotation:

import org.springframework.lang.NonNull;
import org.springframework.lang.Nullable;

public class UserService {
    @Nullable
    public User findById(@NonNull String id) { ... }

    @NonNull
    public User save(@NonNull User user) { ... }
}

After (Spring 7) — @NullMarked makes non-null the default; only exceptions need @Nullable:

import org.jspecify.annotations.NullMarked;
import org.jspecify.annotations.Nullable;

@NullMarked
public class UserService {
    public @Nullable User findById(String id) { ... }

    public User save(User user) { ... }
}

File changes

• content/enterprise/spring-null-safety-jspecify.json — new pattern (id=110, difficulty=intermediate, requires Java 17+), with whyModernWins covering non-null-by-default semantics, JSpecify as a cross-framework standard, and improved static analysis tooling (NullAway, Error Prone, IntelliJ)
• content/enterprise/jdbc-resultset-vs-jpa-criteria.json — updated next to link into the new pattern, extending the enterprise navigation chain

• Fixes Spring Framework 7 with Null Safety check #60

💬 We'd love your input! Share your thoughts on Copilot coding agent in our 2 minute survey.