"The two giants of the component model will eventually match?"
What is .NET? We can discuss .NET and NET technology books from various technical perspectives can also be written
This, even hundreds of hundreds. But Microsoft advocates .NET, the most important purpose is to provide a sufficient and Java
The "Enterprise Platform" confrontation platform confrontation. Microsoft wants companies to use .NET
For the core platform of the enterprise application system, according to this company's core platform, we will develop a variety of application systems.
Mobile device, forming the full information supply chain required by the enterprise application system, providing similar
Current business business in Java. Microsoft wants to pass .NET to enter the corporate market attempt is
of.
Why is Microsoft to enter the corporate market? Mainly because the corporate market is the most abundant market,
It is also the market that Microsoft wants to enter. In addition, Microsoft does not want Java exclusively enterprise market.
In turn produce threats to Microsoft, this is the second key factor. Second, more important reason is, Microsoft
Almost full of saturation in the client, continuing to grow, it is necessary to continue to grow up,
The industry market, the consumer market, the communication market, and the game market are the goals of Microsoft pay attention.
Microsoft wants to enter the corporate market, and it needs to face the J2EE architecture that is increasing. At present, J2EE has been
It is used as a large-scale enterprise for information technology for the core of the company. According to Gartner Group, EJB
The architecture will increase year by year, and it will have more than 40% of the usage in 2003. This representative EJB will become a company
The core component architecture of the application system, more enterprise systems will use J2EE to build.
These phenomena reflects very real and obvious in large information industry, such as Taiwan's desktop (TSMC), and
(UMC) and Friends Optoelectronics are already using Java and J2EE as a core technology developed as a new generation of information systems.
Take a look at the two leadership manufacturers of the EJB server - BEA WebLogic and IBM WebSphere.
WebLogic and WebSphere have become the core J2EE server of many companies, providing enterprise development applications
In addition to the cornerstone of the system, the solution center of the enterprise application system is also slowly formed, and many of them are derived.
New software requirements and applications. For example, many Portal systems, ERP, CRM or Web Service applications are around
Application of value added outside of these two J2EE servers. This phenomenon has begun to form a very huge power,
Let the competition of the EJB server from the EJB core server to the point of EJB solution, just like a black hole is constantly
The new application and power are attracted to use this architecture. This effect is the enterprise information technology
The phenomenon that should be formed, because only this can be expanded. At the beginning of Microsoft
Windows is like this, attracting the world programmers to develop applications for Windows, with Microsoft Windows
For the core of the application, this has created Windows to become a hegemony of the world's client operating system.
It can be seen that a core software technology is the importance of information applications. At the beginning, Microsoft's power on Windows
Push the COM / COM component model, I hope they become core components technology on Windows, providing companies in Windows
Develop a solution to enterprise application systems on the platform. In fact, in efficiency, COM is indeed nice. According to Xu
Multi-test and results published on TPCC, COM execution efficiency is almost best. Frost time THE
The EJB published on Serverside is more troublesome to the city. The Java industry still refuses to admit that COM is efficient than EJB, but in the current data, the EJB of ejb on Windows is far less than COM .
After MICROSOFT for many years, COM / COM does have a good use result. According to North 2002
US information survey about COM shows that people using COM technology account for 34.3%, and 9% of people answered
COM will be used. Although COM performs very well in execution efficiency, it is undeniable that COM can only be in Windows.
Platform use, and inconvenient to use in Internet applications, the ductility is not as EJB, which is COM fatal
Disadvantages.
.NET core components technology
Since Microsoft wants .NET becomes a platform for enterprise applications, what is it to provide? In addition to developing workers
Outside of. Net is the most important thing to provide a software solution similar to J2EE architecture to attract software personnel.
Develop an enterprise-class application system for .NET, help .NET to enter the corporate market and Java platform competition.
What is the technology similar to the J2EE architecture? From the figure below, we can see clearly, Microsoft
Core technology cores with the Sun Java platform are gradually established in .NET. Virtual competition for Microsoft and Sun
The platform is now almost very similar, however, the current Java is far more than Microsoft in the field of component technology.
Provided solutions.
Component technology in .NET is mainly made in .NET components in conjunction with COM . COM is transferred to operation in .NET
The core service of the system provides features of transaction management, and .NET components can
Data perceived components (Data-Aware) with Visual Component, Data-Aware
Component and Middleware (Middleware Component). However, use the .NET component as a .NET platform
There are many problems in the parts. The first is the .NET component must rely on Com components to provide distributed transaction management capabilities;
.NET components are currently not as EJB, Fail-Over and Load-Balancing capabilities, in enterprise applications
It is obviously insufficient.
In addition, .NET components must be used with COM , which means that programmers must develop COM components, and.
NET's native tools cannot develop COM components, and programmers must also use native Windows development tools. this
In addition, once COM is used, it is not possible to port it to other platforms. If Microsoft
Migrating .NET into Linux or FreeBSD, which will not be ported to this .NET application system.
Some platforms.
So, is Microsoft that requires a new one, can I use the component architecture used in the .NET platform? My eyes
Look, if Microsoft wants to position the .NET platform in the enterprise system, it is true that it is true.
This technology, but this is a little difficult for Microsoft. First of all, Microsoft is busy in the last one.
The Java platform spent seven or eight years of results, is busy developing .NET itself, .net development tool, .NET
According to the library, all Microsoft Server applications are placed under .NET, it may not be put into on
Too many resources will develop a new enterprise-level component architecture.
In addition, you can find out how the history of Microsoft builds the component architecture can be found in this regard, Microsoft is indeed unhappy. It is expected that Microsoft defines the specifications of the enterprise component architecture similar to EJB in a short time .NET platform
And it is not easy to achieve it.
Component technical results
16-bit VBX failed
32-bit VBX failed
OLE failed
CoM is still
ActiveX failed
MTS failed
COM is not bad
.NET components are not suitable for use in enterprise applications
Since the new .NET under the enterprise component architecture is not completed in a short period of time, is it representative .NET in this
Aspects have not been able to come out early with J2EE competition? In fact, it is not necessarily, because if you can't develop a quick development
The new component architecture, why not use the component architecture that already exists and has been verified?
Let us think about the characteristics and needs of .NET, you can know what component architecture is best suited to the .NET platform
Become an enterprise-level component architecture.
What component architecture has been used for a long time and has passed the market verification?
→ CORBA, EJB and COM
What component architecture can be cross-platform?
→ CORBA and EJB
What component architecture allows multiple languages to develop and use?
→ CORBA
From the above questions, we have seen the answer to come out. More critical is the third issue above.
Since .NET is a language-neutral platform, programmers can use any language to develop .NET applications, because
This assembly architecture in the .NET platform must be able to develop and use a varger language, not like EJB
You can only use Java languages. In contrast, CORBA is just in line with language. In addition, CORBA is one
A cross-platform component architecture that can be portable to various platforms with .NET. Therefore, from all aspects, CORBA is real
At the core component architecture that is very suitable for use in .NET and becomes .NET.
CORBA and EJB
CORBA has been used for a long time in the enterprise application system, which is mature and has been strictly tested.
Component technology. Many component architectures after Corba have also learned CORBA. For example, EJB in J2EE
Specifications can be implemented using CORBA, and also require EJB servers after EJB 2.0, and CORBA is also compatible, thereby
It can be seen that the importance and maturity of the CORBA component architecture. At present, CORBA is still a component in sustainable development.
Specifications, OMG continues to define more complete core and service specifications for CORBA.
The stub / proxy and component service architecture used by CORBA deeply affects the implementation structure of COM and EJBs, so that
COM and EJB component architecture and CORBA have many appearances.
Since CORBA is almost the ancestors of other component architecture, CORBA is absolutely capable, parts and EJB compensation
ceremony. If .NET can use CORBA as a core component architecture on its platform, then .NET can provide J2EE
As a good business application architecture. Although many people will questioning the implementation of the enterprise application system in the PC is not enough?
However, as 64-bit CPUs (Intel and AMD) are about to launch, Microsoft is also ready to launch 64-bit operating systems.
Under the protection of .NET Virtual Execution Environment, if you add a safe CORBA, then .NET can indeed provide
Combining competitive business executive platforms, competing with J2EE in China / low-order enterprise applications. In this way,
Java / J2EE no longer has an absolute advantage in enterprise applications.
Since CORBA has such a big help for the corporate operation of Microsoft .NET platform, then CORBA component architecture
What kind of architecture will serve in the .NET platform?
Corba for .net
How do CORBA provide enterprise-class services on the .NET platform? Since CORBA uses the IIOP Communication Protocol as an interface to calling CORBA services, traditional CORBA engines (such as Borland's Visibroker) should be
CORBA servo ends and clients generate connectable DLLs or libraries, these DLLs and function libraries are responsible for customers
The end passes the CORBA server of the servo end through the IIOP. Therefore, even if it is executed in the .NET platform, it is also
Use IIOP as a calling communication protocol, as shown on the right.
However, Microsoft under .NET is a communication association using the .NET Remoting mechanism as a remote and distributed communication.
. So, how do the .NET's CORBA development tool combines the .NET's Remoting mechanism, and allows .NET
What are the different languages call remote CORBA services through IIOP?
In fact, this is almost the same as the development of the native window development tool under Windows, only
It is in the .NET CORBA engine to make some additional work to allow .NET development tools and applications
Use CORBA technology.
First, the CORBA development tool under .NET must be able to provide support for the mainstream program language under the .NET, which represents CORBA
For .NET must generate client Corba.Net Stub and servo-servo-servo. Net for each program language
Proxy. Second, in order to combine with the .NET Remoting mechanism and provide IIOP, CORBA for
.NET must generate an adapter and .NET Remotjng as a mechanism for communication, .NET Remoting through this
Adapter calls the bottom CORBA for .NET engine, Corba For .NET engine will put .NET
Remoting
The call convention is converted to the IIOP communication protocol. After the conversion of Adapter and Corba For .NET engine,
You can call remote CORBA services and CORBA servers, even via RMI Over IIOP to remote
The EJB server is as follows:
The architecture described above is still more detailed. Because various program languages under .NET will be transferred by .NET compiler
IL for .NET, thus Corba For .NET tool can generate an IL type client CORBA.NET Stub
.
As a result, no matter what the programmer is used by the programmer, you can guarantee this CORBA.NET.
STUB to call remote CORBA services. This architecture is actually compliant than the CORBA development tool under Windows.
Easy, because under Windows, CORBA manufacturers must also produce customers in different programming languages for different programming languages.
Corba stubs. Now .NET's CORBA manufacturer is easier and consistent because of the characteristics of .NET.
Once CORBA vendors can implement CORBA for .NET under. Net, then not only let .NET's programmer
Send a true enterprise-level .NET application system, more compatible because CORBA and EJB are compatible, so CORBA service under .NET
The instructor can also call and integrate EJB servers through the RMI Over IIOP, provide .NET and J2EE seamless integration.
Force, and allow the user's application system to be able to move smoothly from the .NET platform to the J2EE platform, as shown below.
What's more, now many EJB servers can manage CORBA objects like managing EJB objects, which means
EJB server to perform in Mainframe or UNIX / Linux can manage and integrate CORBA executed in .NET
Object or CORBA service. After .NET has Corba solution, finally entered the enterprise
The ability of the application architecture.
Giants will finalize?
The complexity of CORBA has not been accepted by the majority of programmers. Now Corba itself is very safe, and after the test of the corporate market (even EJB, it has experienced 2
Version baptism), Corba's development vendors should already be clear that CORBA is not accepted by most developers.
Because it is not Corba, it is too complicated in Corba. Therefore, these developers should abandon CORBA for
Transaction Service and Security Services (SECURITY service). Further, if
If CORBA vendors can provide .NET components to package complicated CORBA calls and access mechanisms.
And combine the ability of data access, then programmers under .NET will be able to learn and use very fast speed.
CORBA component architecture. In this way, CORBA will have the opportunity to show up in the .NET platform, have the opportunity to become .NET
The most potent component architecture in the platform will also have the opportunity to make Corba vomit, let the world understand the value of CORBA.
"EJB and CORBA two major giants will eventually be confrontable"? No, more correct statement should be J2EE / EJB finally found respect
The opponent --.net/corba, and Corba and EJB will also enter the era of "both competition and cooperation". Of course, the premise is
The manufacturer launched software products for Corba For .NET.
