[BUG] Description

Hello,

I don't understand why the open api generator generate two kind / approach and of constructor for ApiClient object : one with full autowirred and a second one constructor with no parameter, not annotated with @Autowired

Without having a bean providing a RestTemplate it lead to an "no bean error" at startup of the embedding application and no way to instantiate manually the API classes and ApiClient classes.

The following configuration was used for the generator in Gradle :

openApiGenerate {
generatorName = "java"
library = "resttemplate"
inputSpec = "${rootDir}/XXXX.yaml".toString()

outputDir = "${rootDir}/gensrc".toString()
/*systemProperties = [
        modelDocs      : "false",
        models         : "",
        apis           : "",
        supportingFiles: "false"
]*/

configOptions = [
        useOptional          : "true",
        swaggerDocketConfig  : "false",
        performBeanValidation: "false",
        useBeanValidation    : "false",
        useTags              : "true",
        singleContentTypes   : "true",
        basePackage          : "XXX",
        configPackage        : "XXXX.config",
        title                : rootProject.name,
        java8                : "false",
        dateLibrary          : "java8",
        serializableModel    : "true",
        artifactId           : rootProject.name,
        apiPackage           : "XXXX.api",
        modelPackage         : "XXXX.api.model",
        invokerPackage       : "XXXX.client",
        interfaceOnly        : "false",
        supportingFiles		 : 	"true",
        schema				 : "Bearer"
       
]

}

Regards

Reproduce the generated Java client with the Gradle openApiGenerate configuration shown, focusing on the generated ApiClient constructors and RestTemplate dependency. Trace the Java resttemplate generation entry point and compare the constructor behavior; done means the generated client can be used without the reported startup bean error and supports the intended instantiation path.