. NET and the Java EE what to learn from each other?

Java

Writing this post stems from my experience of both. NET development and Java EE development. In the course of this transformation, I have a lot of clear but scattered ideas about the limitations of the development of a single platform . After the discussion of the method and scope of passing variables between the pages of the Brother Zhen, I am more aware of the development of different platforms, the way of thinking will be so different, the original scattered ideas are constantly emerging in my mind, let me have to write this post impulse. In fact, I have been advocating a point of view: technology is interlinked, proficient in analogy, good association is our programmers should have the advantage. We are concentrating. NET technology, you may wish to take a look at the rest of the work gap. NET outside the world.

Mentioned. NET and Java-EE, will generally think of their fight, fire and not the relationship between, after all, both are trying to capture the favor of programmers, occupy more market share. I don't mean to preach. NET is how powerful, how is the Java EE how mature, also have no intention to explore NHibernate, Spring.net, et cetera. The origins of project just want to see from a programmer's point of view what the two learn from each other in a competitive process, and explore the need to understand two areas of knowledge at the same time. OK, let's get to the other.

Remember that in early 2003, I went to a Dell internship and had the task of creating a Web application for use by a number of closely related departments to increase the level of collaboration between departments. In choosing what technology to do this Web application, I gave up the more familiar ASP, and then chose the asp.net. Just to do this project, I have an indissoluble bond with asp.net and even. Net. At that time the first contact with ASP.net, the first feeling is that it is much better than the ASP, no longer like the writing ASP in the HTML embedded in a heap of scriptlet, dynamic content of the presentation are included in one method, such as Page.oninit () and Page.onload () and so on, these methods let me see the client side JS method shadow. What I need to do in developing the ASP.net page is to introduce different Web control or HTML control into the page, which is similar to the HTML tag controls In addition to it has ASP's prefix and at that time looks like magic General runat= "Server". Such similarity allows me to familiarize myself with HTML and JS quickly with the basic application of asp.net, and I have done the tasks assigned to me with great efficiency, even though I have a request, a Response, Such objects as session and application are not very well understood. Asp. NET's progress is revolutionary, no wonder some friends think ASP.net is the most successful product in the. NET family. I was just taking asp.net to compare with the ASP, its advantages are naturally exposed, especially in the control design advantages. In fact, until later into the development of Java EE area, I still appreciate the development of ASP.net way. Microsoft has always adhered to the principle of weakening domain development features in technology innovation, so that developers can be easily used in different areas of development. Asp. NET has brought WebForm, and in the desktop program development There is WinForm, the two places can be seen everywhere, this allows the original desktop program developers to smooth transition to the Web application development asp.net support for the design and use of controls is perfect, but also for web designers to enter the asp.net development field to remove a lot of obstacles. Back to the field of Java, do swing development personnel, if you want to learn the development of the Web, the original knowledge is almost useless. In this popularity is the era of wealth, in a certain level of common ground, so that developers can Itong, is undoubtedly a very sensible approach. J2eefield is beginning to realize this, the release of the swing concept to web development wicket framwork is a great step forward indeed. Java EE to reduce the difficulty of web development, to attract entry level developers need to. NET to have a good consult.

Good, personal experience goes on to say. At the end of 2003, I entered a software company engaged in the development of Java EE. At that time, the head of technical department in the interview I mentioned the lack of Java EE development experience, I confidently told him that I have done. NET, and. NET and Java EE are all focused on the enterprise application, so it's definitely going to be quick, and there's no problem. However, later work proved that the difference between the platform is very large, from. NET to the Java-EE is not an easy thing. Without the familiar Web control, instead of the simple tag Library, there is no easy and easy-to-use event-driven approach, presenting the seemingly ugly faces of Doget, DoPost, Dohead and service. The process of metamorphosis is painful, but metamorphosis brings about evolution. The change in development mode allows me to look at web development from a more in-depth perspective, and I begin to rethink Web application. The complexity of web development stems largely from the HTTP is a stateless connection protocol, Web server whether you are Michael or Jordon, as long as you use the same URL in the browser, you will get the same resources. Here, you must know what the URL is. Maybe you'll step up and refute what I just said, but this is absolutely true in the age of static HTML pages. With the development of the Times, resources are no longer limited to static HTML pages, followed by the emergence of so-called dynamic Web pages. The dynamic here is not the page full of Flash animation, but the content of the Web page will change according to different request. Although the content of the web began to personalize, it still did not break out of the client-sent Request,server return response such a pattern. Because HTTP is a stateless connection protocol, in order to be able to identify the user access to the same resource state, in the Java EE World, we have to start with the request, response and session of such objects to control the life Cycle of these objects. So, even with the simplest Web application, we must have a good understanding of objects such as request, response, and session. By focusing on these basic objects, we have a more accurate grasp of the flow of the application, better partitioning of the modules to facilitate collaboration between developers. However in. NET in the world, the request and the session such objects of concern is far less than the attention of page, from the Jin River Brother post can be seen. Asp. NET development reduced the difficulty of development, but to some extent hindered the developer to the Web ApplicAtion's overall grasp, as the spring fish Brother's feedback mentioned, too entangled in the relationship between the pages, "not conducive to the overall structure of the system good design." The Java EE application allows programmers to have a good representation of the overall architecture of the Web application. NET still have to make a good effort ah! Suggestions. NET programmer can try to use the technology of Java EE to develop a simple Web application, I believe such a process will give you a further understanding of web development.

The

has entered the field of Java EE, and in addition to the way the development has changed, buzz words has changed. The two most frequently used words are full of daily work, one is MVC and the other is the framework. I am feeling that the pattern in the Java EE use of the universality, regrets in the application of the MVC framework can be implemented to enable a large team to work together to develop a project. At that time I began to believe that the wide application of pattern to software development is a huge and far-reaching changes, but also began to read the "Core Java Patterns" and benefit from it. And in. NET world, the attention to pattern is far inferior to the Java EE, although this situation is changing. When it comes to MVC, you have to make some statements about such a weighty term. The development of JSP has gone through two stages: JSP Model1 and JSP Model2. In the Model1 is the combination of JSP and JavaBean, to a certain extent, to achieve MVC, but the coupling between model and control is still prevalent, and Model2 is really implemented mvc:jsp as a presentation layer, responsible for the display of data The servlet acts as a request dispatcher, distributing the request to a different business module, which is a commander carrying the banner of controller, while Vo is a carrier of data, is the model in the MVC triangle. The concept of MVC is necessary to enter the Java development field, starting with your first simple application, starting with the first article on Java EE development, and the rich open source MVC framework has become a good textbook for us to learn MVC pattern. After a preliminary understanding of Java EE, we can choose some excellent MVC framework to study, such as WebWork and spring. This is helpful for learning the overall architecture design of the system.

Perhaps extremes are really a constant truth, the field of Java-EE in the development framework for the pursuit of madness, we look here: wicket-introduction. You will find that the framework that can be used to develop Web application has reached 55 and is growing. In fact, the weakness of Java development is not control this level, but in view. A lot of genius's energy is spent on repeating the wheel, but there is no way to perfect one or more frameworks, this has to make people feel sad ah! At this point, does Java EE have to learn a good thing from. Net? In the. NET world, the focus should be on the development of controls, a well-designed, powerful control that is an excellent booster for improving development efficiency. A lot. NET developers are spending their energy on designing controls. NET is like a cornucopia, constantly gathering the wisdom crystallization of developers. In the world of Java EE, in order to reduce this kind of waste of resources, the Wicket framework appears. It emphasizes component design and component reuse, and allows developers to focus on component development, thereby enhancing the functionality of the framework is already ease of use. Hopefully, the Wicket framework can bring a little change to the Java-ee world!

Talking, really a bit of a wild horse feel the runaway. I do not know if I have said that for a long time, do you understand my real intention? In this era of technology so open,. NET programmer should get to know the Java EE, and vice versa. I think, learn from each other, common progress this sentence again ordinary but can generalize this Luo wordy thousands of words.