fix: resolve Validation Meta annotations not working (#4886)

[kuntal1461]

---

Pull Request

Thank you for contributing to swagger-core!

Please fill out the following information to help us review your PR efficiently.

---

Description

This PR fixes an issue where Validation Meta annotations were not being correctly recognized by the ModelResolver.

Problem

When developers use composed validation annotations (for example, a custom @MyNotBlank built on top of @NotBlank), swagger-core failed to introspect these Meta annotations, causing validation metadata to be lost in generated models.

Solution

Enhanced ModelResolver to introspect and apply Meta annotations properly.
A new test class ComposedConstraintMetaAnnotationTest verifies correct handling of composed constraint annotations.

Fixes: #4886

---

Type of Change

• 🐛 Bug fix
• 🧪 Tests

---

Checklist

• I have added/updated tests as needed
• The PR title is descriptive
• The code builds and passes tests locally (mvn clean test / gradle test)
• I have linked related issue Validation Meta annotations not working #4886

---

Screenshots / Additional Context

• Verified that composed constraint annotations are now detected and applied.

• No regressions in direct annotation handling.

• Affected files:

  • modules/swagger-core/src/main/java/io/swagger/v3/core/jackson/ModelResolver.java
  • modules/swagger-core/src/test/java/io/swagger/v3/core/resolving/ComposedConstraintMetaAnnotationTest.java

---

[ewaostrowska]

Hi @kuntal1461,
Thanks a lot for providing the PR, it is a step in the right direction to resolve Validation Meta annotations issue.

To be able to merge these changes we need some adjustments:

• [Bug]: SpecFilter skips the ApiResponse#$ref field #4960 fix should be removed from this PR
• resolving Validation Meta annotations does currently work on a path variable in a Controller which means that at least part of the code could be reused in the case of DTOs as well. The logic for controllers meta annotations is in ParameterProcessor and it needs to be adjusted before applying it in ModelResolver. Maybe consider moving it to a new class
• the logic currently recognizes only javax.validation.*. jakarta.validation.* should be recognized as well
• Test:
  - Add the new test using jakarta.validation.constraints.*
  - Test composed constraints for @SiZe, @pattern etc
  - Add a parameter vs. DTO parity test to prevent regressions

[Mattias-Sehlstedt]

Could we add a test that mimics how @Range works? I believe the current implementation might interpret such a structure oddly, since it will parse the "unused" meta-parameters since it does not handle the override functionality.

See class definition below, and the functionality offered by @OverridesAttribute.

@Documented
@Constraint(validatedBy = { })
@SupportedValidationTarget(ValidationTarget.ANNOTATED_ELEMENT)
@Target({ METHOD, FIELD, ANNOTATION_TYPE, CONSTRUCTOR, PARAMETER, TYPE_USE })
@Retention(RUNTIME)
@Repeatable(List.class)
@Min(0)
@Max(Long.MAX_VALUE)
@ReportAsSingleViolation
public @interface Range {
	@OverridesAttribute(constraint = Min.class, name = "value") long min() default 0;

	@OverridesAttribute(constraint = Max.class, name = "value") long max() default Long.MAX_VALUE;

	String message() default "{org.hibernate.validator.constraints.Range.message}";

	Class<?>[] groups() default { };

	Class<? extends Payload>[] payload() default { };

	/**
	 * Defines several {@code @Range} annotations on the same element.
	 */
	@Target({ METHOD, FIELD, ANNOTATION_TYPE, CONSTRUCTOR, PARAMETER, TYPE_USE })
	@Retention(RUNTIME)
	@Documented
	public @interface List {
		Range[] value();
	}
}

Issue basically what is mentioned in issue.

[daniel-kmiecik]

@kuntal1461 thanks for your contribution and for preparing the fix.
Great work on refining the solution and addressing the issue.
Really appreciate the time and effort you put into it!