----- "John Verhaeg" <jverhaeg(a)redhat.com&gt; wrote: > On Jan 26, 2010, at 3:46 PM, Ramesh Reddy wrote: > > > On Tue, 2010-01-26 at 15:53 -0500, Barry Lafond wrote: > > > >> * Maintain current Preview Data and Execute VDB > functionality. > > Unless you are thinking to maintain both Teiid 6.2 along with Teiid > 7.0 > > in the designer this is not possible. > > > > Teiid 7.0 does NOT support embedded version, nor does it work out > side > > the container. > > > > No, we're not planning on maintaining 6.2. The idea, which we still > believe is possible, is to auto-build and deploy VDBs under the covers > that contain artifacts from the workspace, build an appropriate DTP > profile, etc., then use DTP's existing preview capability against that > Teiid source. > Does Designer in its current implementation accomplish preview through admin API calls, or some other non-API magic, like writing to the filesystem? If Preview is accomplished via the admin API, then it's just a few lines of code to get a connection to Teiid from DataTools and cast it to a SPECIFIC version of the Admin API that our (non-datatools) plugins could use. This should apply to any admin API provided functionality. Supporting different versions of Teiid in this scenario would require specific code for each Admin API change, which given our current rate of change is understandably every version. I would be in favor of managing this over releases until we slow down, rather than trying to support multiple versions of the engine in a single release of designer. Too complex and we have to much to do.

It is easy however to support viewing metadata and querying a truly DEPLOYED VDB (as opposed to preview) across multiple versions of the Teiid engine. This I do think we should support. ... > above). Finally, the DTP view that is "given automatically" doesn't > just show up in Designer automatically - we're still anticipating some > development work necessary to ensure the user experience remains as > seamless as possible and to reduce any drastic changes to how things > work now. > Yes, DataTools gives us what we need to view metadata and query, but we will have some work to do to: 1) Deploy 2) Create new connection profile for new VDB. 3) Connect and bring up the DataTools perspective. I also think we have to do some rebranding. Our perspectives, categories, and plugins get a bit lost when you drop them into a big install like JBoss Tools. We have to be more specific than "Designer". ~jd _______________________________________________ teiid-designer-dev mailing list teiid-designer-dev(a)lists.jboss.org https://lists.jboss.org/mailman/listinfo/teiid-designer-dev