Amanuel G. Shiferaw

Your code defeats the purpose of using a standard implementation at all.
imho, you have to base your implementations on abstraction.
I don't understand why you used native sql in this case.

We are using it over here without any issue, at least until now.

BR

Hello Ahmet, the package is generated and added to the classpath automatically on build. In the pom.xml, search for `swagger-codegen-maven-plugin` part, it is this section that generates it. Or else check the git repository README.

I don’t get your idea. Not allowing null is one thing that can solve NPE. But, if you use null or Optional, you have to validate in anycase.

The thing is it misses the point, on leaf nodes there is no need for a wrapper while possible to check directly. Obviously there will be a miss use and may not matter for small apps.

Let's say that a class has 20 fields, should you wrap them all in Optional you will see the difference on performance (even if it might seem negligible). Assume that the method using this class is triggered simultaneously from say > 10000 clients. I leave the calculation to you. I know these days there are monster servers capable of running any app. But, should we consider them or the minimum required enviroment?

Disagree on what, can you explain a bit more?

Imo yet this is much better, rather than wrapping just to check for nullity, wouldn't it be better to check the raw object

Totaly agree, it is very argumentative. Infact it is recommended to be used only class level. Class fields should not be declared Optional. Please check a talk from Stuart Marks, one of the principal engineers: https://www.youtube.com/watch?v=Ej0sss6cq14

Hello Amar,

Thanks for the comment, yes it is a re-write and may depend on the provider. The whole point is whether to keep all history from feature branches or not.

Once you have configured the SSH address and cridentials using the admin console, you add a property to the enviroment variable as " env.SSH_CONFIG_NAME='localSSHConfig' ". Then later to access it with "${env.SSH_CONFIG_NAME}"

You are welcome, glad to hear that.