The objectization in the jsplet is not a smart TRICK, but an inevitable design. Now everyone says oo, but OO means anything, in addition to the words on the book, can you describe it with your own words, can you understand the kind of inevitable. If it is an effective concept, it has a corresponding field outside the software. According to early textbooks, OO is to simulate the real world, this statement is only reflecting a dilemma in design, a kind of thoughts. The most direct significance of object-oriented is to indicate the coupling between state and behavior, which will therene, in the program, can be used to manipulate this aggregate in a program. On the interface, we see a component, in the model layer, what we see is still that object, we can clearly distinguish it in the configuration file. In the action-oriented framework of the action, Package looks like an object, but it is not seen in the Action layer. When we need to use two Action features (such as Role and USER), the previous Action cannot Used, you can only write one. Think about it, how much concept we need, how much work needs to do, in order to create a suitable conceptual framework in the software, how to maintain the tension in this framework.
