J2EE vs. Microsoft.NET - Web Services for the XML architecture I. In this article, we will in-depth comparison of two platforms that can be used to build commercial XML Web Services, respectively, Java 2 provided by Sun Microsystems. Enterprise Edition (J2EE) and the .NET platform provided by Microsoft. Although J2EE represents a public standard, .NET is a standard for a single manufacturer (although .NET tries to get ECMA standards, but only in the most basic part is adopted by ECMA, please refer to http: // MSDN.Microsoft.com/net/ecma/, there is no standardization in the application of the company), and the Java platform is revealed. It is indeed all major manufacturers other than Microsoft to formulate all specifications (please refer to http: / /www.jcp.org, you will find that all Java technology is coordinated to coordinate major companies). Although Java is far ahead, we will still explore only the Web Services architecture of the server. For example: our discussion will not involve Jini or Office XP, we will not discuss Java across Solaris, Linux, Mac OS X, and Windows platforms, and .NET only cross Windows 98 / ME / 2000 / XP and other Windows platforms fact. We will not discuss "cross-language" this Java has already tried to reach, Microsoft is used as a major feature of .NET, but it is not the functionality of this. (See http://grunge.cs.tu-berlin.de/~tu-berlin.de/~tml, you can find that Java has long met so-called cross-language features, SMALLTALK, Eiffel, Lisp, Prolog, Basic and other languages Successfully converted into Java Bytecode, unlike .NET known as a cross-language, there is a monster of Cobol.net. The original language should be made to match the .NET, so it produces VB.NET, Cobol.Net Bundry Products). It claims that the crossword shouts for a long time, it turns out that it is not in the past. After reading this article, you will more understand the extraordinary shortcomings of these two architectures, and will have more clear considerations when developing your company's next-generation Web Services decisions. Ii. Foreword The next generation of distributed operations has been coming. In the past few years, XML is widely used in computer computing environments to achieve a long goal of sharing information on global information online. Today, it can further provide sharing on computing capabilities. From the perspective of technology, the emergence of Web Services cannot be considered a new revolution in a distributed computer operation. It can be structurally rendered, even a message inside, so it is naturally more compelling than an XML application. III. Industrial Standards and Enterprise Standards Through Web Services, any application can be smoothly integrated on the network. The basic principle of Web Services is to transmit XML messages using standard network protocols (for example: http). This is a very lightweight communication mechanism, so you can make any program language, intermediate layer components or platforms easily integrated. Generally, industrial or in-business interior will receive the industry standards adopted by vendors, especially those that have been taken in the market test. With Web Services, you can quickly and low cost integrate two companies, departments or even two programs. To build Web Services must adopt the industry-wide web services technology. Let us now look at what web services is. First you have to know how to build and use Web Services. In fact, Web Services is a very simple XML interface for business, applications, and system services.
It is also to wear the existing technical old clothes. Web Services is actually a new generation of distributed services. Before this, Corba, DCOM, COM , RMI are technically used to implement distributed architecture, and it has also been very smooth; and a new generation Distributed services, using XML technology, such as XML-RPC and SOAP is the best example, a new generation of distributed technology can be used as a basis (such as SMTP, FTP, etc.), but currently Welcome ways are still popular with XML Base in HTTP, but the effectiveness is not the best communication protocol. Even so, these new generations have not passed the test, and maybe they have a successful operation, or some risks may exist. In the face of so many distributed technology, the level of J2EE platforms and .NET platforms is as follows: support for old-distributed technology: J2EE .NET ----------------- ------------ CORBA support does not support RMI / IIOP support does not support COM does not support support for new generations of web services: J2EE .NET ------------- --------------- XML-RPC support does not support SOAP support support from the above two charts we can learn that J2EE supports more extensive for the company for posture-conserved companies Applying for distributed operation services for existing enterprise systems, and .NET platform still only supports the comb COM from COM and DCOM, and its technical predecessor MTS COM is three years earlier than Enterprise JavaBeans technology, and we can infer J2EE. Distributed service than the technology of .NET leads for three years. In addition, the current large host used in the company is CORBA technology, J2EE is of course best on old-specific support, because COM can only run on the Windows platform. If it is an attitude over-garde company, use J2EE to use XML-RPC (http://java.sun.com/xml/jaxrpc/index.html) or soap (http://java.sun.com/xml/ JAXM / INDEX.HTML) Technology, Sun Microsystems is more provided by Java Web Service Developer Pack (http://java.sun.com/webservices/webservicespack.html) for developers to develop Web Services. Confused .NET technology, only provides support for SOAP. In the absence of extensive distributed technical support, the support of the new generation of distributed technology is unable to provide elastic choices, and the risk is large, it is possible to be estimated. Even if the new generation of Web Services is very stable, his stability is often affected by the stability of the underlying operating system. If you choose .NET, it will be tied to recognize the most unstable Windows platform, worse What can only be operated on the official web server of Microsoft, I believe that the friend who uses IIS before, will there be doubted about the security and stability after suffering from Nimda, etc. However, if you choose J2EE technology, in many application servers that follow the standard manufacturers, you can choose the most cost-effective platform, the lowest cost, and also think the best platform. You can check with Http://www.soapware.org/directory/4/implementations Query existing SOAP realms to see how much is a solid work designed for Java.
All in all, we will consider the three aspects of the platform's stability, the stability of the server, and the diversity of the product, and J2EE is completely defeated .NET technology. The following techniques have been used for the industry, but also the best way to Web Services: - Provides Web Services to develop, components and platforms to develop, connect to the Platform Web Services. - Provide Web Services defines web services as WSDL (Web Services Description Language). WSDL files allow others to know the function of Web Services. - Provides Web Services register with UDDI (Universal Description, Discovery, And Integration6). UDDI allows program developers to deploy Web - users to find Web Services through UDDI. - The user's program combines Web Services and calls Web Services through SOAP (Simple Object Access Protoco) or XML-RPC. XML-RPC or SOAP provides a message delivery in XML format on the HTTP protocol. This is a common communication protocol in Web Services. Note that the above mechanism is a way to build Web Services and make it work. Although there are other methods to do, we believe that these technologies are one of the most important and will be widely used. It can be seen that in fact, we have not yet consistent way to build Web Services, and there are still many difficulties in constructing. In the specifications of SOAP, EBXML, and service streams, all family manufacturers have different opinions. And SOAP is most commonly propaganda: independent of program language, regardless of these two features with specific platforms, will completely smash when you try to use the Apache SOAP to communicate with Microsoft Soap Toolkit, completely smash (translation: this is Because XSI: Type properties have a difference in realt.). In addition to the understanding of practical details, more important reason is because some people deliberately destroy the criteria. Even so, there is still a lot of good news for Web Services: - very rare, all vendors, including Sun Microsystems and Microsoft, etc., agree that SOAP, WSDL, and UDDI are potential products, so they Will progress in future products - all vendors are united, together with the standard of establishing Web Services and planting Web Services applications. IV. Develop Web Services using J2EE and Microsoft.net if you want to develop a useful network service system. The challenges faced are not as simple as the surface. Your web services must be reliable, Pu, ⒉ 菀 菀 龃怼 龃怼 ⒂ 匦 匦 匦 蠹 蠹 蠹 蠹 ┭ 邮 邮 邮 堋 堋 庑 庑 庑 庑 ┭ 庑 庑 庑 庑 ┭ 庑 庑 庑 庑 ┭ 谌 ┭ 谌 ┭ ┭ ┭ ┭ ┭ ┭ ┭ 谌 ┭ ┭ ┭ 谌 ┭ 谌 谌 谌 谌 谌 谌 谌 谌 谌 ┭ Polyester τ Trades? NBSPJ2EE and .NET are extension of extension of extension of server-side enterprise applications. Earlier versions of these technologies are not specifically used to develop web services. Today, Web Services has become trend, so two major camps also adjust their solutions, so you can now use these technologies to develop Web Services. J2EE and .NET's common vision is to achieve the basic project of developing Web Services, such as cross-platform XML communication, load balancing, and transactions. Instead of having to write these basic projects, it is better to write an application on the platform that can provide these services.
However, when developing to a certain scale of applications, a certain complexity is generated. At this time, there must be assistance of development tools. If you choose one of the platforms, the tool you can choose is as follows: Development A New Generation Web Services Development Tools: J2EE Platform Tools include: JBuilder (Borland) Forte for Java (Sun) WebLogic Workshop (BEA) JDeveloper (Oracle) Visual, Visual Cafe (WebGain). Only Visual Stdio .NET can be seen here that you can provide the best tools and solutions on your existing business solutions, and you can have the best version of the free basic version. Different needs are best choices, not only to seek tools and solutions provided by a single manufacturer. V. J2EE Java 2 Platform, Enterprise Edition (J2EE) is designed to develop, deployment, and management issues designed to solve multi-layered business solutions. Under the efforts of many manufacturers of Sun Microsystems, J2EE has become an industry standard. For you, the most important thing is that you must first understand J2EE is a standard, not a product. You can't say "Download" J2EE, but download a range of Adobe Acrobat PDF files, which will carefully describe the operational regulations between the application and the container. Through compliance with J2EE, the application can be deployed in a container on a variety of platforms. The Target of J2EE camp is to provide customers with multiple choices of products and tools, and drive the effect of poor currency currency, so that the best products become the winners in the market. The only way to achieve this ideal is that all vendors must comply with J2EE standards. In terms of transaction security, Sun Microsystems cooperates with many manufacturers that provide e-commerce platforms, such as BEA, IBM, and Oracle, etc., together to develop J2EE. Sun Microsystems has initiated a Java standard to organize Java Community Process (JCP), dedicated to the new decisions to improve J2EE. The reason why Sun Microsystems is because the best way to achieve electronic transactions is to invite all experts to develop strict specifications - only such practices can successfully reach their integrated market goals. J2EE is an application of Java. Your J2EE component must be translated into bytecode and execute JRE under the Java execution engine. It is worth mentioning that even the container of the J2EE platform is made in Java technology. It is not long after the official release of Microsoft.NET, published because of the security error (see http://support.microsoft.com/directory/Article.asp?id=kb;n-us Q317396 & SD = MSDN &, I haven't downloaded friends who haven't downloaded it, so I don't know how to reappear, so we should know more about it. It will be decided. Vi. J2EE and Web Services. J2EE is located in the conventional Java program language to develop the architecture of the servo application. It can be used to build traditional websites, software components, or web applications (Web Application). Recently, J2EE is more expanded into standards that support XML Web Services.
These Web Services can communicate with other Web Services developed with J2EE or non-J2EE standards. The J2EE application exists in a container that provides services required by an enterprise-class application, and of course, the quality required by the company, such as transaction, security, and personistence services. The business level is responsible for business procedures and information logic. In a large-scale J2EE application, commercial logic is built using Enterprise JavaBeans (EJB) component technology. It can be seen that this level is dedicated to business procedures and processing logic. It can connect to the database through Java Database Connectivity (JDBC), SQL / J, or connecting existing systems through Java Connector Architecture (JCA) technology. It can also use Java to process XML API (JAXP, Java API for XML Processing) and connect to the commercial application provided by other coordination vendors through Web Services technology (including: SOAP, UDDI, WSDL, and EBXML). Therefore, efforts manufacturers can make J2EE programs connected to each other through Web Services technology (including: SOAP, UDDI, WSDL, and EBXML). So just use Java Servlets (this is a Java technology that supports HTTP request / response), you can accept requests from the Web Services of the Cooperative Vendor and respond. Java Servlets uses technologies such as JAXP / JAXR / JAXM / JAX-RPC to provide all features of Web Services operating. Web Services is currently the existence of the expansion link, which is currently in incorporating web services into the J2EE's next version, and becomes a standard for the industry. Traditional client programs, such as Java Applets, or desktop applications, will connect EJB components directly to Internet Inter-ORB Protocol (IIOP), without disclosing Web Services, if you want to use Web Services, but because of the usual client's application Will be with the J2EE app from the same vendor, so do not need XML Web Services to play the role of communication, even if there is really need, there is no problem. Browsers and wireless devices can be connected to Java Server Pages (JSP), which have all enterprises using HTML, XHTML, or WML design. Vii. Microsoft's .NET platform Microsoft .NET is a product that allows companies to develop intelligent and enterprise-level web services. Special attention here is that .NET and J2EE are the biggest difference: .NET is a product strategy, while J2EE is a standard. Microsoft.net can be said to be a big renovation of Windows DNA, which is a platform for developing enterprise-level applications before Microsoft. Windows DNA contains many existing products, including Microsoft Transaction Server (MTS) with COM , Microsoft Message Queue (MSMQ), and Microsoft SQL Server database. The new .NET Framework is designed to replace these technologies and add to the Web Services hierarchy and the improvement of programming language. The .NET application exists in a container, this container provides services needed for enterprise applications, such as transaction, security, and message services. The business level of the .NET application is developed through the .NET Managed component. This level is responsible for business procedures and data logic.
