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

[Van Halbert]

I vote the designer doesn't push the creation of a translator by adding additional translator properties to the vdb.xml file.  If the user created a custom connector, they'll already be dealing with the task of deploying it to server(s).   Also, if this information is stored in the vdb (call it A) and then if the original custom translator is changed (and replaced) and then vdb "A" is  redeployed, don't we now have a usability issue that has to be resolved on whether to replace the existing translator properties or not.   Carrying stale information in the vdb has caused us problems in the past, so I would hope we wouldn't head back down that road on the first release.

I think this first release should be simple and focused.    If the usability in the next release drives it in this direction, then so be it.   


On May 25, 2010, at 12:39 PM, John Verhaeg wrote:

> On May 25, 2010, at 11:21 AM, Ramesh Reddy wrote:
> 
>> What I forgot mention in the earlier is, if user chooses one of the
>> default "translators", then there is not really any need to define the
>> XML fragment for the Translator at all inside the vdb.xml. Which I
>> suspect in majority of the cases. Only when user wants to alter the
>> default behavior, Teiid would need the additional translator fragment.
> 
> 
> So presumably there will be some property on the translators that indicates whether its a default translator?
> 
> Thanks,
> 
> JPAV
> 
> 
> 
> 
> _______________________________________________
> teiid-dev mailing list
> teiid-dev at lists.jboss.org
> https://lists.jboss.org/mailman/listinfo/teiid-dev

Van Halbert
Principal Software Eng.
Red Hat, Inc.
------
vhalbert at redhat.com