See a reprint articles, and please think about and discuss!

  See a reprint articles, and please think about and discuss!    In the next five years, Java Platform, Enterprise Edition (Java EE) will no longer be the standard procedures for mainstream design model, Burton Group senior analyst Richard Monson-Haefel predicted that the SOA and lead to the development of the reasons for this result one. 

  Last week, the Burton Group has an earthshaking things, Monson-Haefel published an article, entitled "JEE5: Java EE预示outcome of the threatened".    Java Platform, Enterprise Edition is like a prehistoric animal, as a whole because it could not rely solely on too large edible plants to survive and lead to extinction, Burton analyst said that in the spring with the release of JEE5, Java Platform, Enterprise Edition has become too complicated lead to the development of enterprise-level staff to use it, they are increasingly looking forward to the emergence of alternative version, for example, Ruby-on-Rails. 

  Monson-Haefel conclusions as cruel as death certificate: "JEE5 in the complexity of the failure is预示the Java Enterprise Edition platform from the end of the field of enterprise development platform on the rule of the defeated. Consider all enterprises in the development of new enterprises should be Multi-reference to some other platforms, and enterprises should also make early preparations to deal with as enterprise solutions the ultimate demise of Java EE. " 

  Java Enterprise Edition platform development will be the inevitable follow some previous standards, such as CORBA (Common request broker architecture), which was also very promising, but in the end or towards the decline, he said. 

  "Five years, the Java Platform, Enterprise Edition will become the 21st century CORBA," Monson-Haefel said.    "People will look at it say, 'It has also盛极一时', but because too complex, now nobody wants to use it." 

  He emphasized that his efforts are only Java EE platform reveals the decline of the road is not the Java language. 

  "Java programming language is not in any danger of" the analyst said Burton.    "I think the Java programming language in the past few years will be to continue to develop as the backbone of enterprise development." 

  Monson-Haefel is not the only one forecast Java EE platform and the SOA failure as the cause of the results of one of the reasons analysts. 

  "Java EE is now time is running out," ZapThink, a senior analyst Jason Bloomberg said that he also saw the consequences of this result is the chief culprit in Java EE each new version of the increase in complexity.    "Obviously, as long as the release of the new version of the module, or increase, the only only increase complexity. End, it will be crushed by their own. Judging from the current view, the future is not developed than the existing Java EE more streamlined version. " 

  Even if the complexity of the first put aside did not say when the need to enter the service-oriented enterprises of this new era, SOA and Web services as an expert in the field Bloomberg on the Java platform has already seen its fatal flaw. 

  "From the fundamental point of view, Java EE is not for the world created by the SOA," said an analyst at ZapThink.    "Now, you can rely on the J2EE-based run-time infrastructure, and many in Java for the realization of SOA products create fantastic realization of the SOA. In fact, a lot of Java - an object-oriented programming language, a virtual machine infrastructure, Java and the Java EE is a realization of specific n-tier structure of the framework, unfortunately, any side of Java, or any of the virtual machine is not suitable for the development of SOA platform. " 

  Java EE achieve in the object-oriented (OO) does not fully conform to the core of SOA - service-oriented, Bloomberg argued. 

  "From the point of view of the object-oriented services and services example is the same concept," he said.    "Object example of this is independent of the existence of a set of concepts little value in the SOA." 

  Java EE in the virtual machine is not the best solution for SOA, Bloomberg said. 

  "Virtual machine goal is to enhance code portability, but the SOA, interoperability is more important," he said.    "In the SOA, if you do not need mobile code, then why should overcome these difficulties to achieve code transplant? Fundamentally speaking, the Virtual Machine distributed computing approach is the object of the serial to achieve remote method invocation, But SOA is a fixed interface to achieve the exchange of information between the services. " 

  Monson-Haefel from the point of view of the uniform makes service-oriented platform (such as Java EE) needs to become more irrelevant. 

  "SOA is a public procedure reduces the degree of importance of design models," Burton analyst said.    "What is really important because the service is no longer in communication model, but the communication itself, which is you are exchanging data, which is complete with your close relationship with the exchange of data, rather than the data behind the programming model." 

  Java EE main advantage is to provide a common programming model, but when the field for the development of SOA, this is not the most important.    Monson-Haefel said. 

  "SOA and Web services to reduce the background to the importance of the operation," said an analyst at Burton.    "This is how the two stressed the mutual cooperation, for instance, the XML Web services and HTTP how to cooperate with each other. Background to the operation have been unimportant." 

  Finally, the company ZapThink Bloomberg said: enterprise-class JavaBeans / Servlet / Java Server Pages framework inconsistent with the SOA. 

  "As you can see, the focus is Java EE for scalable n-tier provide a framework that is the big deal with the affairs of the site needs," Bloomberg said.    "However, if you was to create an enterprise-class SOA framework, then you have to be completed in the Construction and Java EE platform under construction on the large diameter of the tribunal. You need to create the framework is activated and maintenance services for the abstraction layer Centre, which is crucial to the SOA. Therefore, Java EE is very suitable for the platform based on the day-to-day services, but not SOA. " 

  From: www.csdn.net 

  My own experience: 
  I was released from weblogic5.0 started learning to use java, is not a long time, but then I remember that the Internet is relatively rapid development time (probably in my place), almost every week the mandate of the construction site, php3 and asp is then used most, when I saw jsp when I have only one idea: good!    Then we all know that.    Net beta out, I did not use j2ee done relatively large applications, I can not comparison.    Net and java is good or bad, but at that time. Net really scared me jump!    Now. Net is not as good as expected.    Have anything comparison, I have two system a bit confusing!    We all talk about their own views!    10 million Biechao Oh! 

  Posted on 2006-07-15 16:51 sosopro Reading (99) Comments (0) edit their collections quoted Category: Java Learning Notes 

Share and Enjoy: These icons link to social bookmarking sites where readers can share and discover new web pages.
  • Digg
  • del.icio.us
  • Facebook
  • DotNetKicks
  • DZone
  • Netvouz
  • Propeller

Recommend Articles

Comments

Leave a Reply