Tim, The built-in ORM in CF9 is Java's Hibernate under the covers. What I expect to see in MVC frameworks that use a current ORM like Transfer or Reactor will probably provide an ability to use the native ORM engine when CF9 becomes gold. There may be a benefit in performance with using a native ORM versus another object factory built into your framework.
The viability of providing for the new ORM would have to be based on the levels of effort of syntactical changes, ease of integration, performance testing of transactional sites, and stability. Current ORM(s) work in two distinct ways. Pre-generated, stable, model components deployed and an application cached object factories. The new CF9 ORM may remove the need for one or both of these approaches, but I am not sure yet. I would have to see where the objects are stored, managed and how much control I as the developer have to influence this. If anything, it is a possible new approach that can be an option for future release of frameworks. I do not think it will make any existing ORM frameworks null and void as adoption rates of CF servers, currently existing applications, and time/developer hour investment to change out currently embedded ORM(s). If you are creating something brand new, this is definitely future fodder for some late nights of introspection. Cheers, Teddy
