I. preamble
In this white paper, we will make a powerful comparison in two products based on XML-based Web Services for commercial companies: Java 2 platform designed by the solar microsystem, Enterprise Edition (J2EE) 1, and another It is Microsoft's Microsoft.net2. In this article, some views may take you, but we hope that most of these points can communicate with you! So when you read this article, please remember the three commitments: 1. We promise: when you compare, it is on a reasonable, neutrality and no biased basis! 2, we promise: tell you our true feelings about these two technologies! 3. We promise: eliminate your uneprical factors about these two technologies in the market! Although J2EE and .NET covers a lot of technology and standards, we will clearly focus on this point to Web Services. After reading this white paper, you will find that our comparison of these two technologies can make you choose when designing Web Services! First, the first half of this white paper is based on Web Services, J2EE and .NET section. If you have already mastered these technologies, you can skip this section, enter the second part, where you have interest on the two comparisons!
Ii. Introduction
The second generation step-by-step processing has arrived. In the past few years, XML enables different types of processing environments to exchange information through Internet. It provides a simple way to share programs, data. In the past few years, business companies provide their products and services through the Internet. Do they have Web Services? With regard to the definition of Web Services, the CEO of Mind Electric, is the CEO, which is defined in this: "Integrate a set of functions into a separate entity, shared by other users or programs through the network. Web Services' role is to establish a sub-program for open step-by-step systems, enabling companies and individuals to build a small-scale expenses of their worldwide applications! "Before Web Services arrived, the integrated enterprise application is difficult Established, this is because the standards of different programming languages and software in all organizations are also different. Two commercial systems that use the same language and the same middleware are almost impossible to encounter. These factors make people headache in a comprehensive application, and ultimately lead to so-called "middleware" shared with other systems. Simply put, the synergy between these systems is bulky, and it is painful! But with Web Services, any app can be integrated with a long time. The basis of Web Services is XML message delivery, which is passed through standard network protocols, such as HTTP, which is a very easy communication mechanism for any programming language, middleware, and platform, which makes the system between systems. The ability to work is relaxed. These industrial standards have been widely accepted, and these techniques are low-risk for companies. With the support of Web Services, you can integrate two commercial systems, departments or quickly combined two applications, and these are efficient! These services are presented in these services to register themselves through public or private business registration systems. These Web Services will complete themselves, such as interface structures, service requirements, service methods, and conditions they need! Users who use these services understand the functions of these web services through these descriptions. Web Services will be beautiful, when a service is called, it will naturally call other services to complete this work and give the user a completely user-friendly experience! In order for these services to act dynamically, they need to share information through the user's authentication. Create Web Services through technologies that have been widely used
Behind Web Services is a complete theoretical system, let us see how to create and use a web service. Web Services is now just old technology to wear a new hat, it is now just a simple XML-based interface. Some of the techniques of the following technologies have been accepted for most industries, which will be a WEB Services method: Suppliers choose their own programming language, middleware, and development platform development, assemble web services. Each vendor defines a Web Services Description Language (The Web Services Description Language4) to establish Web Services through unified language and standard. Suppliers are registered in UDDI, UDDI enables suppliers to publish web services, and find their software to find services provided by other vendors, that is, share! The user searches for the service he wants through UDDI. The user calls the service's operation through the SOAP (Simple Object Access Protocol). SOAP provides a method similar to XML to draw parameters and returns a value via HTTP. This is a protocol that all web services abide by. Note that these techniques are only for simple Web Services. For business transactions, multi-request transactions, programs, file streams, and extended business transactions, requires a structure that has been fully protocol, and the requirements for these applications often exceed SOAP-based implementation. This is the motive generated by EBXML, a set of XML specification interconnected programs to provide a comprehensive basis for a B2B collaboration. Note that the above method is just one of Web Services, you can also have more choices, but we feel that these methods are extremely important will be used in a wide range of industries! In fact, we have not yet achieved the full agreement of Web Services, and there are still many other solutions, such as SOAP expansion, EBXML, and service flow descriptions, but they have not reached a consistent. But we also have good news: the vast majority of developers, including Sun and Microsoft agreement on SOAP, WSDL, and UDDI, which provide a good foundation for the future. All developers are jointly establishing the standard of Web Services. The J2ee and Microsoft.net If you want to build a web services that makes it easy to use, you have to make your web services ratio, highly available, canable, upgradeable and can be accepted Complete the task under. These needs are not distinguished from any other enterprise app. J2EE and .NET are evolved from existing application servers to establish these enterprise applications. In their earlier versions, these technologies are not used for web services from history. Now the Web Services era has arrived, these two camps are redesigned their solutions on their respective platforms, and any platform can meet your needs of the WEB Services. Similar work like XML, balanced load, transaction processing, between J2EE and .NET, both have too much similar. You can easily write your program through the services they provide, rather than writing every programs alone as before. This will let you focus on writing the module you want to strengthen the function.
If you are engaged in a financial services company, you are very familiar with financial services, but you can understand the Web Services program compared to Technologies such as Sun, IBM, BEA, Oracle and Microsoft. You only need to buy their related packages, you don't have to be a proficient programming expert to build a financial service-based Web Services. You can find the problem that you may encounter at any time in your business affairs, because this part can be programmed by yourself, while other trivial programs are written to resolve the package you purchased! Now, we start to see the details of J2EE and .NET. Iii. J2EE
The Java2 platform, the Enterprise version (J2EE) is designed for a single complex issue, such as multi-level enterprise solutions such as relevant departments, staff configuration, project management. J2EE is an industrial standard proposed by Sun Microsystems. You should realize that J2EE is a standard, not a product, this is very important. So you have no way to "download" J2EE. You are more suitable to download a set of protocol documents between the application and the package in the Adobe Acrobat PDF format. As long as both parties are obeyed from J2EE, their applications can run in a wide variety of package environments. The purpose of the J2EE camp is to enable all users to choose their own products and tools, which also encourages the competition between the products. This purpose is the implementation of J2EE has become an industrial standard. To make users rest assured, Sun has other Ebusiness platform developers (like the BEA, IBM and Oracle) to define J2EE. Sun also launched Java civil organizations to make new programs to constantly improve J2EE. SUN did this because they have to do this to fight for success, they want to become industry standards. Java: J2EE's Basic Language J2EE System Construction The basis of the Java language. Java most exciting place is that he uses the programmer to write a code, you can run on other platforms, as follows: 1. Developers write source code with Java. 2, Java code is compiled into a zona code, which is a cross-platform intermediate code, where the source code and machine code are. 3. When these code is run, the Java Run Environment (JRE) explains this bytecode and executes simultaneously. J2EE is the application of Java language. Your J2EE component is converted into bytecode executing under JRE. J2EE and Web Services J2EE view from historical views is an architecture that uses Java language building server-side applications. It creates traditional websites, software components, or application packages. J2EE has recently been extended to include support to establish XML-based web services. These Web Services can interact with other web services. J2EE Web Services Development Model As shown in Figure 1: Figure 1 Brief Explanation: J2EE application is a group of enterprise applications, which are integrated by many necessary servers, secure service programs, etc. Business processing and data processing is performed on the business floor, and most of these are built in the J2EE application, these are established with Enterprise JavaBeans (EJB) Components. This layer completes the database's connection through Java Database Connectivity (JDBC) or SQL / J or existing systems using Java Connector Architecture (JCA). Of course, Web Services technology (SOAP, UDDI, WSKL, EBXML) can be used, which are implemented through Java API functions. Business partners can share J2EE applications via Web Services Technology (SOAP, UDDI, WSKL, EBXML). A small servlet accepts the request from the Web Service from the business partner. Servlet uses Java's API to perform Web Services operations. Traditional "fat" customers, connect directly to the EJB layer directly via the EJB layer, so there is no need to collaborate with XML-based Web Services. The web browser and wireless devices are connected to the JSP, and the user does not have to care about the interface between HTML, XHTML, or WML.
In order to provide a detailed description, Sun also provides a reference tool for J2EE. The programmer is written to ensure portability of its components. These tools should not be a product, they are just the role of testing. Additional Services All manufacturers that support J2EE platforms provide additional services, of course, these are not found in the industry standard, so it may affect the granting capabilities, such as extended EAI functionality, e-commerce components, advanced B2B integrated. There are other features, such as balanced load, is not affecting program code transplantation because their service is provided by the underlying package. Iv. Microsoft's .NET platform
