[teiid-dev] Translators in the "vdb.xml" file.

[Ramesh Reddy]

Taking a second look after functionality of the translator and
connections factories, 

Translators are immutable across all the deployment environments. Once
defined they should never change from environment to environment.

Currently they are defined in global scope. i.e. a given translator
instance is global to the Teiid runtime instance, that is shared among
VDBs. This makes them to defined in their own deployment file. 

However, if VDB need to be migrated to another environment, the user
will also need to migrate the corresponding translators. This adds
complexity in terms of migration. This can be avoided, by making the
translators VDB scoped, by defining them inside the "vdb.xml" file.
Then, they go along with VDB, so need to for migration of multiple
artifacts from environment to environment.

As per functionality this will not change any thing from what has been
discussed before. This adds minor additional changes to "vdb.xml", and
VDB, translator deployers. Translator functionality Designer would need
to designed such that they are written to vdb.xml, instead of calling
Admin API to create a translator. I will make changes to the vdb.xml's
schema file note the changes required.

Thanks. Let me know if you have any questions.

Ramesh..