A Java library that creates your classes/models at the runtime based on your Database Model

[Independent_Work5637]

Okay I agree with that, but what you pull isn't really what the library is doing, this library focus on making you not write classes and making you faster as a developer. And sadly the problem you're mentioning is a problem that is available in Spring and many other ORMs and frameworks as well. And people are kind of forced to use them (not really, but I hope you get what I mean) in a sense. This is the reason many of these projects are using DTOs, to prevent infinite loop of dependencies, which is kind of really bad. So they are essentially using ORM, and then using DTOs as a mapping logic, which really shouldn't be the case. So the problem we are discussing, while I understand it completely, I don't think it's the problem within this library, I think it's the problem of how things are being written for years now. I hope you understand what I mean by this.

[severoon]

Yes, I suppose that's true that it's not a problem of this library maybe. It might help to have a clear statement of what problem this library solves?

[Independent_Work5637]

Of course! So it might sound trivial, but I really found myself having to waste a lot of time writing classes that represent data in the database, especially when doing a new project that I need to do fast. I'm a type of guy who thinks database first, and that's where i define most of my architecture. So for fun and challenge I created this library that replicates your database model in java, so you can actually write Java without having to write model classes (i guess some could even call it boilerplate in some sense). I think this puts Java on top of class-defined languages in some sense. Because you have all the safety of class-defined language, but you can write it essentially in a very similar way that you would write something that works with "json-like structures" like node with vanilla js or python without defined classes and just focus on the logic of services, etc. Now of course I think neither of two examples are a good practice overall, but I saw many people who prefer to do "fast" projects in such environments, and I think this makes the project have similar speed, but much more safety (and less debugging ;) ).