How do you recognize the framework?

I am new to the world of programming. I work with Java web applications. I am learning struts2 / hibernate / spring.

I think, instead of reading hibernation from textbooks, it is useful to read the full source code. Basically, I plan to study the full code of the framework, understand how caching is performed, how transactions are processed, how several threads are processed, etc.

Have any of you done this before? My intention is that if we recognize one specific structure inside and out, it will be very useful for application development.

+4
source share
4 answers

The best way - the easiest way: Build something! Start small, but think of it as an incremental, iterative exercise and add features that cover all aspects of the framework you want to cover. Browse as many books, blogs, and posts as possible to learn more from people who have previously used the structure and applied what you learned. This is the best way to learn the full stack structure!

+2
source

You learn the framework and programming, how you learn to do something even better: spend a lot of time on it. See this question and its answers and its duplicates. Keep reading, learning and experimenting. Start building small projects. You're on the right track, go on.

0
source

Diving right in the frame code is not a great starting point. Here's how you should progress:

  • Think about the project you want to work with respect to the structure, i.e. project idea
  • Inability to satisfy point 1, just follow the examples in the official documentation and try to get your hands wet from things
  • Help people on IRC / forums as this will surely make you dive deeper than regular stuff
  • Look at the error messages and try to make sense of things. Do you understand the problem in consideration? If not, you can take a look at the “Developers Start Guide” for this project.

But I would like to note that, although knowledge of the structure inside from the point of view of the code can be pleasant, it is certainly not a requirement to use the framework efficiently. That the whole point of using the framework (except for reusing the wheel:>).

0
source

To begin to understand how the platform solves your problem, you often need an example that is much smaller than a full-featured framework. Since all of your examples cover web presentations to varying degrees, I suggest Bruce Tate's “Bitter Java”. This is a great example of presenting a very poorly written web application, and then reworking it to improve it. This will give you a good idea of ​​the MV2 architecture on which most modern frameworks are based.

Frameworks are simply “enhanced versions” made reusable by asking you to provide your “plug-in content components”.

0
source

All Articles