JSF will not repeat the mistakes EJB

1.Sun the only technology on the ruined EJB

Sun introduced its own technology, has always been very self-confident, even a little conceited to the extent of self-confidence. Because of ego, Sun does not always willing to promote the technology, and planning a little ingenuity, blindly look to the attractiveness of the technology itself, as if the Expert Group pedantic they shouted, they will arise from those clouds of sensation. This is a commercial society, the emperor's daughter is still unhappy marriage, not to mention you are a liquor, but also superstition what sell themselves?

EJB's fate has dealt a blow to Sun, do not know if Sun has not woken up. Why such a great server-side EJB component architecture, will lose even Hibernate and his ilk? EJB really is too complicated? Perhaps, but not the EJB living to the point of the root causes of this predicament. Only technical theory, ignore the user needs, turned a deaf ear to the voice of the programmer, is Sun's biggest weakness, this weakness affected the release of all Sun technologies to their business plan is always tepid EJB source.

EJB's rich content, I am afraid that only Java "cattle people" who can appreciate. I have heard more than one Java "cow" and praise of the EJB. High level of abstraction, reasonable structure, stable performance and adaptability omnipotent, large-scale enterprise applications using EJB development is the "cow man" who is the only choice.

Unfortunately, EJB complex concepts, esoteric terminology and heavyweight framework, so that large numbers of patience and love "technology fast" discouraged programmers. On the contrary, publicity-seeking Hibernate, its simple configuration, easy to understand the rules and so-called "lightweight" object encapsulation, because the programmer likes to vote in the Java arena was able to quickly became popular, as doing my part of the star. Things change, so EJB shake their heads, do nothing.

Hibernate EJB's advantages and shortcomings will not go into here, if given the chance, I will also discuss the author and readers. The disrespect of the Hibernate, Hibernate's supporters do not want angry angry. As a tremendously popular Java ORM technology, Hibernate Java programmers have long been widely accepted, its founder Gavin King is now the fame and fortune, to the points of criticism, or be able to afford one? Moreover, as Gaving King joined the EJB group to standardize the development of EJB ORM, EJB and Hibernate turn hostility into friendship, now a person. As a family, and I complained about something, right when everyone is "contradictions among the people" to handle it, huh, huh!

2. Strikingly similar history, it will repeat itself

The reason that Hibernate and EJB, not to deliberately no judgments of a pass, but to explain the technology to promote Sun's planning on how lightly. Carefully JSF technology, then take a look at JSF Java Web community complaints, you will find that today's JSF and then EJB, exactly the same situation.

First of all, and, like EJB, JSF is an advanced technology. Trying to build a Java Web's UI framework, Fuzzy programming and Web programming Java Desktop line, so that a large number of programmers on the desktop programming experience, can be applied to Web programming intact, this is any other Java Web frameworks have thought of;

Second, and, like EJB, JSF also has a very complex concept. In the JSF "simplify Java Web development" goal behind, is unprecedented technical complexity of JSF. Connectionless nature of HTTP protocol, and respond to the request processing mode, determines the complexity of Web programming, especially Form processing and complicated, is inevitable. Since the JSF, the programmers do not have the face of these complex and cumbersome, then the framework must face. This is the JSF complicated reasons. Of course, the basic JSF programming quite simple, but deep into the JSF's internal, you need to know including the JSF request processing lifecycle, including many complex concepts;

Again, and, like EJB, JSF is also a lack of tools. When we use all kinds of IDE to easily write the desktop program, expected to be difficult to imagine, the lack of these tools support, back 20 years ago, the big picture of how the program will be. The importance of tools can not be overemphasized. JSF is designed for the tool, but, JSF is launched, the tools available meager, even now, visual JSF page editor is also rare;

Finally, and, like EJB, JSF is also a victim of bad business promotion plan. Not timely introduction, then introduced the relationship between untreated well and JSP, but also no large-scale business promotion, JSF only by its own technical advantages, and competitors deal with.

EJB Hibernate then have to contend with, today's JSF Struts and so there next to sneer at. History is strikingly similar, and strikingly similar history, they often continue to repeat itself. Bear to recall the fate of EJB, JSF to repeat it? Sun, please tell us the answer!






Recommended links:



2007 PLM Inventory



Hong Kong dollar 76 million a formal decision to auction 3G licenses



Peel WPS: Jinshan's insistence or abandoned



VOB to Zune



Recommend E-Commerce



Great Friends With The Compatriots In Taiwan Noted Connected With The Download Tool



Important That The Structure, Not Quantity



Hot PIMS And Calendars



Easy to use E-Mail List Management



ASF Converter



VC + + dynamic link library (DLL) program in layman's language (1)



VOB to MPG



Fax Tools Report



Operators around loose charges tariff war is inevitable that the first



Quad Band Swivel Screen Cellphone With