[ https://issues.jboss.org/browse/TEIID-4807?page=com.atlassian.jira.plugin... ] Steven Hawkins commented on TEIID-4807: --------------------------------------- But you are comparing apples to oranges. In the old case the admin method was asking for the ddl specifically for a single schema. In the new case you are returning the metadata for the entire vdb. In the xml case you are returning a different set of metadata that the ddl case - that is not consistent. The model element will still include all of the metadata tags, including "imports", and ddl - plus the additional full ddl. That's not likely what the user would want. There are two different usages being considered there. One is informational - what is the schema contents for a given model. The other is the conversion aspect. It's the latter we we are not offering a 1-1 conversion. We are offering ddl that does not reflect the deployment state of the vdb, but the runtime state. That is functionally different until we only have a full online metadata system. -- This message was sent by Atlassian JIRA (v7.2.3#72005)