`ReturnedClass` eagerly resolves input parameters resulting in logging for parameters that are potentially not required

[lrozenblyum]

We're using Spring Data 3.5.5 and face the warning

ReturnedType - No constructor parameter names discovered. Compile the affected code with '-parameters' instead or avoid its introspection: OurDtoClass

Apparently it is printed after #3225

However in our particular case it seems redundant:

in our repository we have a single method returning that class

@Query("""
		select new <OurDtoClass>(optionItem.id, optionItem.name, optionItem.path)
		from #{#entityName} option JOIN option.optionItem optionItem
		where ....
		""")
	@Override
	Set<OurDtoClass> find...

and for this particular case Spring Data should have no issues with parameter names - we call the constructor explicitly in the query and don't need any guessing - the arguments will be referenced by their natural order and not by names.

Is it possible to remove the warnings for such cases?

[mp911de]

The log message is situated in a code path that is commonly required to evaluate processing of projections. We evaluate projection information eagerly (e.g. in constructors) to avoid synchronization later on when objects are used concurrently regardless of whether the query is using constructor expressions.

Several code paths that evaluate ReturnedType.getInputProperties() are not related to string-based queries at all. By flipping evaluation orders we should be able to defer access to input property resolution, but that will only work for a rather distinct set of cases (constructor expression must be present, no additional dynamic projections, no keyset scrolling).