Re: [teiid-designer-dev] Potential Designer Source Bindings Strategy
Now I get what you mean by "sandbox." I can't really envision a Designer
user having registered different types of Teiid servers (dev, test, production) within
their Designer instance. Seems like the user would register one or more of the type they
are concerned with (i.e., just test, or just dev, or just production). I can see multiple
Teiids being registered when the Teiids are running different versions for one example. To
mix the type of Teiid seems extremely dangerous to me. You can correct me on this if these
assumption are not valid.
I still like the idea of the hidden VDB unless we get rid of the whole preview idea
altogether (which is not going to happen).
----- Original Message -----
From: "John Verhaeg" <jverhaeg(a)redhat.com>
To: "Barry Lafond" <blafond(a)redhat.com>
Cc: "teiid-designer-dev" <teiid-designer-dev(a)lists.jboss.org>
Sent: Thursday, March 25, 2010 2:49:44 PM GMT -06:00 US/Canada Central
Subject: Re: [teiid-designer-dev] Potential Designer Source Bindings Strategy
On Mar 25, 2010, at 8:51 AM, Barry Lafond wrote:
D) I'm still struggling with the concept of a "SandBox" Teiid. If a user has
multiple Teiids and there are Connector Types that don't reside on ALL Teiids, then as
a user, I'd have to work a little harder, switching between "SandBoxes" as I
try to create source models, wire them to different Teiids for the purpose of
"Preview Data ". I think the Hidden VDB concept is still the cleanest paradigm.
User need only Import/Create Sources. Create View models. Assign/change/swap (DND) models
to connectors deployed on any Teiid and the Preview Data just works. I can also have a
source model bound to connectors on multiple Teiids. As long as we decorate (via Model
Explorer AND Execution/Connectors/Teiid View) this connectivity we should be good to go.
I'm not trying to introduce a new concept here by talking about a "sandbox"
Teiid. The fact that we're assuming the user can do things like preview against some
Teiid automatically makes that Teiid a "sandbox". In other words, this isn't
a production Teiid in any way that's administered by some IT group with a bunch of
rules concerning who, when, and what can be deployed.
All I was saying is that the user has to choose which of the potentially many Teiids they
have configured in Designer to treat as a sandbox (i.e., use for preview and test
execution). We could allow them to choose more than one, but we'd certainly always
"default" to just one in particular I'd expect (the first or last one setup
for preview/execution). The user may also have connections to other Teiids that they
aren't allowed to "play" with, such as testing servers or even productions
servers, for which maybe the only thing they can do is retrieve connector types or import
VDBs for instance.
Thanks,
JPAV
_______________________________________________
teiid-designer-dev mailing list
teiid-designer-dev(a)lists.jboss.org
https://lists.jboss.org/mailman/listinfo/teiid-designer-dev