Borland Janeva: Connect .NET and Java
what is
Janeva
?
There are several big companies with leaders in the software industry, each has its own distinct technical features. Microsoft back
Relying on the operating system, Oracle is based on the database, Sun is called the small machine, and IBM is "solved the four seas.
"As a call. As for Borland, it is naturally a professional manufacturer of development tools in the impression of the average person. In fact, Borland
Although starting with development tools, it has gradually changed to a manufacturer of enterprise-class overall solutions in recent years.
Products involve development tools, modeling tools, databases, middleware, demand analysis, change management, and more are many areas. In IT industry
In the war, Borland did not have a specific camp, and its product line spans Windows, Linux, UNIX,
Main platforms such as Java, .NET. Because of the play of this role, Borland coordinated and mutually coordinated each platform.
Communication technology, occupying unique position in the industry.
Borland Janeva is a new product released by Borland and C # Builder. From the literal,
Janeva's name is made up of two words of Java and .Net, which indicates that it is an easy connection to Java.
And .NET technology. Like most people, the author began to pay special attention to Janeva. Until continuously
Telephone or Email in the technical department of large software companies, after consulting Janeva's technical details and sales situation
This is interested in Janeva.
After a period of study, the author is slowly familiar with some technical details and market positioning of Janeva, and it is also
Solve why these software companies are interested in Janeva. When discussing with company colleagues, everyone is also unanimously recognized
For the Janeva is a very technical feature, it is also very marketable products, and it is expected to play in the future enterprise architecture.
Important role.
So what kind of product is Janeva?
According to Borland's documentation, Janeva's feature is Platform Interoperability for the Enterprise,
Note Two critical situations, one is Platform Interoperability, one is Enterprise. Janeva offers from .NET
Seamless interoperability of the platform to the J2EE / CORBA platform, through highly scalable, secure Internet Inter-ORB
Protocol (IIOP?) Makes the client or server-based .NET application can access J2EE and CORBA services
Components on the instructor. Janeva is provided in the form of .NET components, so it is convenient to embed any mainstream .NET
In the environment, you can include Microsoft Visual Studio .NET and Borland C # Builder. Janeva can also be
Support for the programming language of the common language runtime under the .NET platform (COMMON LANGUAGE Runtime).
In the enterprise market, J2EE is in the day, more and more large applications are based on J2EE solutions. except
In addition to the core application based on WebSphere, WebLogic, and other J2EE servers, it is also derived.
Various solutions in different industries, can be said that J2EE is already rooted in the server, it is difficult to shake.
Comparison, Microsoft has an absolute advantage at the client. In particular, MicroSFT is released after the release .NET architecture,
Ambitious hopes to turn the .NET architecture into the enterprise market. According to the analyst's prediction, the possibility of Java or .NET is very small. In the foreseeable future, Java and .NET common melons will appear.
The situation of the field.
It is undeniable that Java and .Net are very excellent Framework, and it provides distributed component technology.
Good support: Java provides RMI, .net provides .NET Remoting. In their respective fields, these two solutions
The program is working very well. However, as mentioned earlier, how to face the situation in Java and .NET, how to
The problem of mutual communication between the two platforms is shocked, because whether it is RMI or .NET Remoting,
Unable to connect to the other party. Especially large companies, inevitably need to face between heterogeneous platforms
The problem, so they are particularly concerned about this kind of communication solution, which is rational.
Heterogeneous platform communication solution
There have been some solutions for heterogeneous platforms before Janeva appear. One of the more famous
It is Web Service. Web Service can be used to access objects on remote machines, using standard XML files as
The format of the data package. Since its specifications are simple and open, it is mostly in any platform and programming language, there are many
The mainstream platforms and languages provide support for Web Service, including Java and .NET. indeed,
With Web Service, object access between Java and .NET can be implemented. In theory, through the Web
Service, you can implement object access between any platform as long as they provide support for Web Service. therefore,
For a while, Web Service became a very popular noun.
Figure 1: Schematic diagram of Janeva solution
But in practice, people will soon find that Web Service is not an ultimate solution. The reason is that,
Web Service has the following defects, and these defects are almost impossible to overcome:
First, the Web Service technology itself is relatively simple, but in order to communicate through the Web Service.
Extra architectures must be performed with the client, and the original object is packaged and exposed. This will need to invest extra money
The source is programming and maintained, more importantly, involving changes to the server. In some key applications,
It is extremely high for reliability, so the system that has been actually verified to stably operate,
Risk is very big.
Second, the simplicity of Web Service technology is convenient for development and maintenance, but on the other hand,
It also brings enough defects that support certain advanced features for distributed component technology. Web service for transaction processing,
Safety features and support for the characteristics of service quality, have always been difficult to issue, and because of the sexuality of Web Service itself
Quality, it is difficult to appear ideal solution in the future. It is easy to understand that in the field of enterprise applications, the above characteristics are not
It is difficult to support or support enough technology. It is difficult for it.
Third, the Web Service uses the standard XML as the format of the data package, although the best compatibility is obtained.
And simplify development, but also results in performance loss. XML character stream and traditional binary flow, processing
The amount of information can be different from one order level, plus the encoding / decoding process, and the gap is greater. Therefore, in some real-time systems that require demanding performance requirements, Web Service is basically not considered.
Another solution is called "bridge", ie bridge technology. This technology uses a special bridge,
As the server and client transit station. When the client sends a request to the server, the bridge converts the request to the server.
Ability to understand, then forward to the server. When the server is transmitted, it is also transferred through the bridge. obviously,
This bridge solution also has problems with performance and compatibility.
Advantages of Janeva
In contrast, Janeva cut into a unique technical perspective, which makes us admire Janeva's setup
The talented concept of the talents. Janeva is provided in the form of .NET components, it is a set of Assembly compliant .NET specification,
Therefore, it can be very convenient to use in .NET development, just import the corresponding package name, you can access Janeva.
Objectives and methods. In the bottom of Janeva, Borland's engineers have achieved a complete IIOP protocol through IIOP.
And the remote objects on the J2EE / CORBA server interact. This architecture of Janeva has the following advantages:
With Janeva solutions, there is no need to make any changes to the server, and the impact on the client is also reduced to the most
Little extent. Due to the direct use of IIOP communication, the service will think it is communicating with a J2EE / CORBA client.
Therefore, there is no need for an additional architecture. In the client, the J2EE / CORBA object will be automatically mapped into the local object of .NET
In form, you only need to program it for this object. In this way, it effectively protects existing investment and technology to avoid because of the frame.
Risks caused by changes.
Figure 2: After importing the EJB package, CS file automatically generated by the mapping mechanism is based on the full compatibility of IIOP, so it is based on the full compatibility of IIOP.
The advanced features of technology have good support. Janeva can support two-way submission transaction, encryption, verification, authorization
Waiting, etc., as well as various complex data types (mapping of CORBA and J2EE). So Janeva
Fully adapt to complex enterprise applications.
In Janeva's solution, the data stream is a character stream like XML, and it is also province.
Go to the encoding / decoded overhead and do not require any bridges to transfer. Therefore, Janeva has sufficient performance.
Guarantee, related test data indicates that Janeva and Web Service solutions are 2 to 40 times in efficiency.
Performance gap. Janeva is a well-deserved choice in a system-demanding system.
Janeva's future
The currently published Janeva version is temporarily supported from the .NET client to the J2EE server side. in
In the list of subsequent development plans, Borland announced a range of new goals, including from the Java client and .net
The two-way connection of the server, the perfect support of the J2EE middleware of WebSphere, WebLogic, etc., and
Other high-end features. It can be expected that Janeva will have a very important position in the future distributed component market.
