Using the model name as the connector name is fine for default scenario,
unless there are two models that are associated with same connector.
On Tue, 2010-03-02 at 10:11 -0500, Steven Hawkins wrote:
Hello all,
There seems to be some confusion over what's needed for connector binding names. To
simplify things, there are two basic requirements - we need a known/stable/not
environmentally dependent name for each connector binding used in a vdb and there also
needs to be a way to associate that name with an actual JNDI resource. In the case of
non-multisource models, the model name itself satisfies the first part. Only in the
multisource scenario do we have an issue with needing an additional vdb specific name for
the connector binding. As a first cut it seems fine to say that both the JNDI mapping and
the vdb specific naming of multi-source connector bindings is a deployment time concern.
Then the only design-time concerns become the model name and optionally marking a model
multi-source enabled.
Any thoughs?
Steve
_______________________________________________
teiid-dev mailing list
teiid-dev(a)lists.jboss.org
https://lists.jboss.org/mailman/listinfo/teiid-dev