It is necessary to understand the book of "enterprise application architecture model", which is more and more discovered that this book is really a classic.
Under the current conditions, we must continue to study the enterprise system. It seems unobsive, but still hopes to continue to pay attention.
on
Spring, I have seen some development documents, or I still don't know what it is, continue to study ING.
The book of "Robert. C Martin also needs further research, but it seems that the style is not the type I like, I can get a job.
About IOC, there are some blurred awareness, but there is not much to really understand
Further attention is needed for distribution and Web Service. recent
Windchill can learn from the part of the permission management, its architecture is really good, but it seems to be too big for a J2EE application, which leads to a lot of function, but there is a lot of flaws.
Also, after Windchill training, it is found that simple HTML performance seems to be too weak, and it should be considered weak. Applet does not loses a good solution, but due to the speed problem of Applet, you can place it in the selected schedule. Other solutions, such as
XMLHTTP,
XUL and
Flash, these nouns need to go to research, or template language, such as
Velocity,
FreeMaker, etc. can also be considered. For template language, my point is that it can be effectively separated indication of layer code and simple expression code, and the function seems to be stronger than pure JSP, but it is limited. For the way of fat client, you can go to research. However, this will inevitably involve data transmission, it seems
Web service is quite good, everyone drills into it. Traditional HTTP transmissions may not meet the needs.
What should I do with the unit testing, database tests? Seeing a novel idea, at least for me, establish a database for every test, but I suspect that this approach has too much impact on the performance of the test. Or don't go to the database at all, you will not connect the database.
Mock Object's way, such specific practices are not clear, but doubt the effect of this practice. As for our current way, individuals feel good, but for maintaining pure test data, I feel that it is better to establish a test database for each level. Specific methods are also discussed. Yes, there is
Dbunit This kind of thing also needs to take time research, see what benefits can be brought about for our unit test
