big spring boot project that have different parts such as :
Models
Socket
Rest API
...
My project includes the all in one maven module.
But I want to break down it to one parent maven module and two child module named "model" and "socket".
Everything is fine yet.
But assume I want to use swagger in main module now.
So I have to use swagger in model classes too such as @ApiModelProperty and etc.
In this case my "model" module must have dependency on swagger too, while I think its not good idea that "model" module (which is only some pojo classes) have dependency to swagger too.
Which is the besrt practice in such cases?
Do I have to include all sub-module in main module?
OR
Is it better that break down main module to several smaller modules (in this scenario)?
Thanks
No answer???
Hello. Personally, I don't see any problem that your pojos need annotations. Annotations are just runtime metainformation. They are idle until they become processed. So unless you're loading your pojos in some env or handling those annotations any other way, they are equal to comments. In general. In this particular situation I share your concern. If those pojos are core classes, framework agnostic, then they should not operate such terms as "API model property". If I were you, I wouldn't bother much and used annotations in that module. If that module won't ever face swagger then annotations become just comments. Regarding best practice. You're right, that module shouldn't depend on anything. But there's no silver bullet
Обсуждают сегодня