Are You Using OMG's Model-Driven Architecture?

Mazzaroth queries: "Over the last few years, system architects saw many middleware and language eras. RPC, CORBA, .Net, EJB/J2EE (with WebLogic, WebSphere, and the zillion of other apps servers), XML/SOAP, Java, C++, C#, to name a few. More recently, an effort has been initiated to isolate application's architecture from the middleware particularities: Model-Driven Architecture (MDA). The idea is pretty good. This will eventually allow me to model the application, deploy it on .NET, then change my mind and go for WebLogic instead for instance. Even if the number of software engineering tools supporting MDA is quite limited for now, I would like to get feedback from people using an MDA approach to develop their application. What are the drawbacks, difficulties and limitations of MDA? What would be required in UML to better support MDA? What percentage of code can actually be generated? Can you share your experience?"