Java 2 Enterprise Edition and .NET
Author: ZDNET CHINA
Date: January 29, 2002
Http://www.zdnet.com.cn/developer/news/story/0,2000081594,20036759-1,00.htm
MDR-EDO: Welcome everyone to Javalive! Today's theme is the Javatm 2 Platform Enterprise Edition (J2EETM) and .NET. The functions of these two work platforms can cover many identical areas, such as web services, so it is very natural. Many people have questions about what is more meaningful to put J2EETM .Net, in order to answer these questions, we are honored to have a well-known author and consultant Jim Farley, "Distributed and Enterprise Computing". Jim is the main software designer of the IT Center of Harvard University. It can answer everyone's question, then we will start now - Who will mention the first question?
Mrweb: Many people think that .NET is better than J2EETM on the design concept of the web, because .NET is designed for Web service. J2EE is just a release (that is, adding the APIs JAXP and JAXR to the platform), do you think this view is valuable?
Jim Farley: This is a good problem, and some people often ask such questions. There are many practical examples here, and Microsoft spent a lot of effort to redesign its infrastructure, which is to make it suitable for Web services. As an open standard, J2EE is naturally tracking, and upgraded some of its protocols, specifications. But if you compare the merchants and the merchant (such as Microsoft and BEA, IBM), then you will find that in the Java field, there are many blurred web service solutions. For Java groups, if these fuzzy concepts become specific, Java's development will definitely be better.
Al-Bandy: In the next few years, you think J2EE and .NET competition, will eventually have a winner or two?
Jim Farley: I can't predict who will be the last winner. Microsoft has its own unique market operation. At the same time, J2EE also has its powerful inertia and strength. I think they will effectively use the business space, and exist at the same time in a short period of time.
Bob Rodes: In my opinion, the main difference between the two is in the level of the standard, .NET is more conserved, J2EE is more open. Is there a comparison of transactions with landscape or vertical? .NET is faster, but will be limited to the Microsoft platform, J2EE slower but is not subject to platform restrictions. Is it because it is too simplified?
Jim Farley: It's just a relative concept, and there is a lot of such factors in measuring the amount of transactions. But unusuried is that .NET is the best choice for Wintel environments. However, there is no factor in the J2EE architecture that hinders the business to develop J2EE operating environments similar to "Wintel-Optimized" (of course, there are many malicious dealers).
Nigelk: Using XML now in Web services has gradually independently independent of platform or technology, it is a better tool or platform to provide a better tool or platform.
Jim Farley: It is very correct. In the ideal environment, these two platforms should be unrelated in Web service specification and support infrastructure, and integrate with "SOAP / WSDL / UDDI" should be a good opportunity. However, the "Value-Add" issue of the general merchant will still exist (Microsoft is a biggest business, but it is not the only one with conservatively psychological business). Unproductive This additional factor will make the web integration will be as difficult as the market maturation. Fogus: As Microsoft thinks C # is the concept of Java, how do you understand? Why can we only choose one?
Jim Farley: If you can ignore the platform problem, then strictly say that you have to do some people: What kind of grammar / programming model / object model do you like best? For my personal opinion, these models have no clear boundaries, but the platform will make this hard specification, Java is the foundation of J2EE, the C # and general operational environments are the basis of .NET single platform. Therefore, C # with Java is actually returned to J2EE to compare this problem. Net.
Joe: For Java PET SHOP, Microsoft has made a lot of improvements in .NET and its performance, code reduction, etc., what is your evaluation of this? Is the .NET speed is really faster?
Jim Farley: I think, it is obvious that this is just a means of marketing. I think the so-called code is just a scorpion. If I just make the code for easy management, this is not a wise move, and it is not aware that it is really meaningful to the infrastructure. If you want to compare different merchants, you can only compare their performance, and you cannot compare the highlight characteristics of .NET's overall infrastructure in J2EE.
Al-Bandy: What is the function is .NET can be implemented and J2EE can't be implemented? At the same time, what is the function is that J2EE can be implemented and .NET can't be implemented? Is there any obvious difference between the two?
Jim Farley: If you want a complete answer, you may have to take a lot of time! If you want more to learn more, you can check out that the article I have written in Software Development mentioned. Here, I can only say that .NET is very good at XML and Wintel integration and J2EE has advantages in convenience and selectivity.
David from Bofa: Depending on what you said is impossible between J2EE and .NET, there is no significant difference in boundaries, then for a beginner, which is more suitable for beginners to learn (assuming must choose one).
Jim Farley: If you are more difficult to get from the content, you have to see which type of business you work, what you like, your future technology / market planning is many factors. If you plan to do some forward-looking jobs in Microsoft's only use Wintel (whether for individuals or business), then .net is preferred. If you think you are not the only business, but to consider competition from other platforms, or you want to develop your own products and customers on other platforms, J2EE will be your best choice.
JoE: J2EE and .NET tools seem to follow W3C standards (SOAP, WSDL), then which one is not standard, self-enclosed?
Jim Farley: In fact, they indeed follow these standards, but the merchant will also "include and extend" their tools (for example, add "value-added" extension to the package protocol, or define payloads for hard drives, etc. ). Therefore, if they follow SOAP / WSDL /, then you don't have to worry. But correctly or not to see Microsoft and J2EE. MRWEB: According to I understand, .NET infrastructure does not support sustainability, if this is the case, this will be a big defect.
Jim Farley: From a certain extent, this is true, COM (a constituent model of Net) does not support automatic continuous management. At the same time, EJB also requires CMP, in a sense, this is indeed a defect in .NET (advantageous must be absorbed). However, many people think that using effective "Delivered Value", using EJB for sustainability management and motivation to run on the J2EE platform, it is better to concentrate on other fields, like web services. I personally agree to this view. However, from another aspect, I think that active communication with Java, which will take each other, and will finally achieve breakthrough achievements, so we should have two attitudes in J2EE.
Greg: If this is developed with Microsoft's CRL competition, how will java develop? Because for Microsoft, CRL is a powerful development tool that allows developers to apply time code to the system without making additional jobs. What reacts in Java?
Jim Farley: I don't agree to use CRL in a multi-language environment to achieve this view that "does not increase the additional workload of developers". You should learn the variable syntax of the CRL structure model and ".NET-IFIED" language. However, about Java's response to this issue, we have seen and heard the anti-response of multilingual support as Java, etc. In the past, although these achievements did not mean that it had been successful, there were many cross-compilers for JavaTM virtual applications. But until now, I haven't seen Sun and Java groups want to have a detailed plan in this field, of course, I have no meaning.
Nigelk: Do you have some statistics or conjectures about J2EE and .NET in the unified market sector? Do they participate in competition in the same market? Still Microsoft intends to reduce your own scale in its traditional field?
Jim Farley: This is a very good problem. Now there is no hard statistical number around me, and I don't believe any statistics because they have some prejudice. But now some of the information we have heard is largely pair, Microsoft is not a choice but is like .NET transformation - this shift will be a greater and more expensive shift. .NET now attracts many SMEs, because not only the cost is low, and Microsoft's tools have great advantages. But many typical big companies are still worried that different development environments require coordination of different merchants, so, for them, Java is more applicable. Of course, I am not saying that the business will not develop in another direction, this is just some of my personal opinions.
Terian3: The above discussion on the use .NET basically focuses on its convenience, then you have any opinions and ideas for the normalization of .NET CLI and C # (like Mono Project). What is the impact of the success of the NET's NON-WINTEL operation environment? Jim Farley: I think the Non-Wintel for .NET is a strong impact on the market, but it must be supported by Microsoft. Although Microsoft has declared its disclosure and participation in standardization (subject to restrictions), its infrastructure is still under its control. In this way, if there is no Microsoft support, so repeated, in the next version will be increasing and worse with .NET compatibility. If Microsoft agrees to bring CLR / CLI to Linux and other Non-Wintel platforms, there will be a dramatic shift in future competition. Take the J2EE and .NET as compared to another standard. However, if so, there will be a big change for Microsoft's development direction, and the results will be very surprising (like Sun publishing its Java source program).
Sachin: When comparing J2EE and .NET, from the Web service perspective of balanced existing system investment, where is the biggest conflict between the two?
Jim Farley: What is the specific value of "Bang for the Buck" in your concept? If you just want to put the product into the market as soon as possible, then most people are interested in Microsoft's products (especially Visual Studio). If you refer to the long-term development of ROI in an existing infrastructure investment, then I think J2EE will be the last winner.
Chris Riner: I want to learn more about J2EE and .NET so that you can make more in-depth comparisons and learn their related technologies. Can you give me some suggestions about this book or information?
Jim Farley: I just thought of me, I haven't mentioned my book, "Java Enterprise In a nutshell". As for .NET, there are a lot of information about it, like O'Reilly and Prentice Hall, but I can't think of the specific name. Generally speaking, find some objective information that is not biased to learn, those articles with certain subjective color are not the best choice.
Nigelk: The comparison between J2EE and .NET is different from other old platforms or technologies. Despite this situation, I think, because the functions that the two can provide very similar, there is no clear reason to choose which tool for specific choice. To make a choice of technology or experience with your own business.
Jim Farley: Yes, I will say that this is correct, I have already said that everything is everything - technology and experience is a powerful factor, and additional factors are enterprise models, user needs, and market development trends. As far as I personally experience, there is no such thing as the .NET needs special platform and closure. Therefore, the J2EE platform is my choice. However, there will be a lot of situations. As we mentioned, estimating the characteristics of both, selecting a suitable thing.
MDR-EDO: Time is really fast, thank you today's participation, and we also discussed a lot of problems, of course, I would like to thank Jim to answer our wonderful answer.
