Richard Soley, the chairman and CEO reviewed the standards of standardization for the standardization of the newly distributed software system (including Web Services). OMG proposes a series of standards such as CORBA, MDA, and UML. The following is the chief contributor Darryl K. TAFT of Eweek in the last month and Soley.
Eweek: What is the current situation now?
SOLEY: Web Services is now like 1991 CORBA and 1994 COM [Microsoft Components Object Model Component Object Model]: It is still a very new technology, and it is still lacking some important services, such as performance and Transaction. But an important difference is that all people have accepted Web Services, which is quite different. This means that there is a good implementation, and then you can build your own service. Web Services is certainly not a brand new technology, which is impossible. Web Services is just a term. I saw the entire industry so recognized, I am very happy, but as a developer, I am more interested in developing an application and easily deploying it to different schemes of different periods. That's why we want to discuss the reasons for the MDA (model driver architecture), because if I can automatically generate and connect between the application modeling system and the underlying architecture, data format and data transfer ... only need to care about the business logic of the program, Toths. If you want to catch fashion, you can generate for Web Services; if the company needs, you can generate for CORBA, or for COM architecture. More importantly, when new things appear, I can also generate corresponding applications.
EWEEK: What is the acception of MDA [Model Drive Architecture]?
SOLEY: MDA accepts a slower in the small company, but in large companies have been quickly adopted, the reason is simple: it does change the way software development - even if you already have mode of modeling. Companies that have already carried out modeling work is usually the case: first there is a modeling team, they find out the implementation of the business, design a model, then write it down, apply a variety of colors, bind, distribute Give developers, put them on everyone's workbench. The developer held a warm discussion on the model, then returned to the workbench, continued to work in front, and threw the model aside. This happens is that the model and realization have no direct relationship. The MDA is that the model itself is also a workpiece developed. Using the compiler to dynamically generate and implement architecture such as J2EE, .NET, CORBA, COM-associated data conversion, persistent storage, conversion integrity, data format, etc., and even get Web Services, we have from UML to SOAP (simple object access Protocol) and WSDL mapping. Therefore, take a model-based approach, you don't need to create things that developers don't need, in fact, your work results will automatically generate code.
Eweek: What is the meaning of open source to MDA?
SOLEY: Open standards keep our specifications, all people can accept, not by the control of a developer, and open source can make us accept one of everyone accepted, not by a developer's control The combination of both is very powerful. This implementation you can not use it, but at least in this implementation, you can use it when you need it. You can use it when you need it. You also know that OMG requires a corresponding implementation before receiving a specification, OMG has adopted a lot of open source implementation, which is very satisfied. Eweek: Some people think that OMG can play a greater role in the Web Services field, what about your view? SOLEY: This is what we have to do. The current situation is that we need to focus on our most good areas. I can tell you two main areas we are working hard. First, we must ensure that MDA is fully supported by Web Services. We have just ended a standard formulation, in fact it has been released on our website, and there have been six implementations. Now you can automatically generate the corresponding WSDL definition and soap file header by a UML model, that is, you don't have to look at those annoying agreements. In addition, there is a mapping corresponding to CORBA. Therefore, if you already have a CORBA architecture, I hope to use it to implement your Web Service-Bim, Bam, Boom, this is no problem. In addition, what I consider is more exciting long-term intent, not now the achievements, you are the missing things in the discussion of the WEB SERVICE - transaction, safety, persistence, and even manage, name service, directory, etc. . We have worked for these things for these things in Corba and COM, now we have to do it all about the UML model, generate the corresponding Web Service implementation. This is our current job, of course, it has not been completed yet.
