I'm working on a big project, which uses beans in a way I can't understand and I don't know how it would be solved.
In this project bean classes have an empty constructor and a big amount of methods, no state.
These methods have a single line which is an invocation of methods contained in other classes (Managers).
I've been told it was done to avoid the loading of all the methods (in bean classes) when JBoss started, so it's lighter.
What other way would be good? How to make code more structured and clear, without losing performance?
All these methods (now in managers) are big, would the solution be shredding the big ones into smaller ones (same for classes)?
Consider that some methods contain like 1000 lines of code. It's a legacy project
posted 2 months ago
Any idea? Or is any way I can make this clearer?
Let me tell you a story about a man named Jed. He made this tiny ad:
RavenDB is an Open Source NoSQL Database that’s fully transactional (ACID) across your database