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

[Barry Lafond]

This sounds too hackish to me, so I'm pushing back... again... :) 


    • Designer has no real concept of a "translator". We deal with Connection Profiles and NOT Server/Teiid properties. It only needs a translator to perform runtime (query) operations. 


    • 
The Properties that we do pass you for the addTranslator() method will be provided from Teiid in the first place, right? The keys will be from Teiid's PropertyDefinitions. 

    • 
Teiid cares about translator.xml files (or whatever they are called). Teiid Designer really doesn't care other than to make sure one exists within a VDB, if that is the new requirement. 

Barry 

----- Original Message ----- 
From: "Ramesh Reddy" <rareddy at redhat.com> 
To: "John Verhaeg" <jverhaeg at redhat.com> 
Cc: teiid-dev at lists.jboss.org 
Sent: Tuesday, May 25, 2010 11:11:11 AM GMT -06:00 US/Canada Central 
Subject: Re: [teiid-dev] Translators in the "vdb.xml" file. 

On Tue, 2010-05-25 at 12:05 -0500, John Verhaeg wrote: 
> 
> But we don't really want to own the format of these translator files. 
> Can't we just modify the admin API method in question to hand us back 
> the translator files so we can then write them to the vdb.xml? 
> 
> 
Designer is already building a properties object for the Translator to 
be called with Admin API. What I am saying is, I will provide the 
schema, which will be similar to "model" fragment with bunch of name 
value pairs. Designer can use that to build the XML. If you are using 
JAXB for xml marshaling it would be no different. 

This also removes the verbose call to the Teiid runtime, so that this 
can be done with out active server connection. 

Ramesh.. 

_______________________________________________ 
teiid-dev mailing list 
teiid-dev at lists.jboss.org 
https://lists.jboss.org/mailman/listinfo/teiid-dev 
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.jboss.org/pipermail/teiid-dev/attachments/20100525/e4d5680b/attachment.html