Each frame has its specific design mode (or something called thought, spirit), which reflects the way this framework solves the problem; this design pattern directly or indirectly determines the way we use the framework. If you can properly grasp this mode, you will use it to your heart, comfort and natural; otherwise, it may become a grievous.
Sentimentary time, I always feel that I can't think of it. I always feel that I have to change something to adapt to my business, so I have added a bunch of excess code; today I have realized, in fact, I have been with DBForms's spirit. DBFORMS is also designed according to MVC, but it may just be a thick particle size on the code, so I think of course add some Action; if I have not guess, the author wants to achieve business processing through JSP (plus Up to Interceptor and custom webevent, so when I enforce a layer of action, try to do something about Controler, using it to be so awkward, a lot of things you want, you know very well Where is it, but you have to get it. It is always so hard. It is not the source code to do some frameworks have been done. This makes me very frustrated, and even want to give up this frame; later, think about it, many simply In fact, you only need to deal with DBFORMS's road to deal with data, it will not be so awkward.
To this, dbforms is the only one I have seen without writing JavaBean, just configuring the underlying Schema data; DBFORMS provides persistence functions, if it is a simple business, it should be developed; The business is more variable, more complicated, DBFORMS does not apply, according to the current experience of the current use; DBFORMS implementation is nothing more than a few cases
1. DBFORMS comes with the basic data processing function, specifically the data operation implemented by DatabaseEvent
2. Interceptor, this can handle many businesses
3, custom DatabaseEvent, or 2 combination
The as the above method may be not enough, or it is very painful.
With other frames, always feel that you have repeated, a bunch of profiles, a bunch of Javabean, a bunch of similar code, feel uncomfortable; and, I still have an idea, I can use AJAX to optimize DBFORMS. Always feel that it is not fast enough ...
