3:44 a.m.
Sorry Ramesh, I seem to have ignored this email.
Ken and I discussed this today. I don't think there should be a ConnectionProfile for
each source. We could create profiles for each of the source we support, but I think
there are two strong reasons not to.
1. The ConnectionProfile for non-JDBC sources would only be usable by our importers. For
example, were I to create implement the DTP connection framework for Salesforce, I could
modify the importer to the resulting ConnectionProfile. But to have the rest of the DTP
framework use the ConnectionProfile I would have to implement the getting of the metadata
for DTP, and the mapping of the query API to DTP, etc. It's a lot of work with no
real value for us, and if we didn't do 'all' the work, it would be confusing
for a knowledgeable user of DTP.
2. Some of import sources don't have a connection. XML to Relational and SOAP
relational don't have to get their metadata from a 'connection' at all. As
often as not the metadata comes from a file on disk, and the connector points elsewhere.
This doesn't mean that the importer or some other action can't produce the info
needed for the ~ds.xml.
~john
----- "Ramesh Reddy" <rareddy(a)redhat.com> wrote:
Is there going to a "Connection Profile" for each source
that Teiid
Designer going to import/access in DTP? I know in previous versions
Designer kept profiles locally, I am not sure the new behavior with
DTP
in the mix.
On Mon, 2010-04-12 at 10:05 -0400, John Doyle wrote:
> ----- "Ramesh Reddy" <rareddy(a)redhat.com> wrote:
>
> > On Fri, 2010-04-09 at 13:55 -0400, John Doyle wrote:
> > >
> > > It's not, it's DTP specific.
> > >
> > > I exported this in clear text, but encrypted is the default.
> >
> > Then for Teiid purposes it is not useful. If this file is in the
> > "-ds.xml" format, Teiid could use it. Is there a way we could add
> > "export as.." feature may be?
>
> For sure, should be pretty easy.
> >
> > Ramesh..
_______________________________________________
teiid-dev mailing list
teiid-dev(a)lists.jboss.org
https://lists.jboss.org/mailman/listinfo/teiid-dev
1:01 a.m.
New subject: Fwd: [teiid-designer-dev] Connection Factories
agree, this does not make sense other than the relational sources using
DTP. Designer can use Teiid to create the CF and DS for the source and
keep a copy of all the "-ds.xml" locally *if* needed by exporting them
back from Teiid.
Ramesh..
On Wed, 2010-04-14 at 14:44 -0400, John Doyle wrote:
1. The ConnectionProfile for non-JDBC sources would only be usable
by
our importers. For example, were I to create implement the DTP
connection framework for Salesforce, I could modify the importer to
the resulting ConnectionProfile. But to have the rest of the DTP
framework use the ConnectionProfile I would have to implement the
getting of the metadata for DTP, and the mapping of the query API to
DTP, etc. It's a lot of work with no real value for us, and if we
didn't do 'all' the work, it would be confusing for a knowledgeable
user of DTP.
2. Some of import sources don't have a connection. XML to Relational
and SOAP relational don't have to get their metadata from a
'connection' at all. As often as not the metadata comes from a file
on disk, and the connector points elsewhere.
This doesn't mean that the importer or some other action can't produce
the info needed for the ~ds.xml.
5136
days inactive
5137
days old
1 comments
2 participants
participants (2)
-
John Doyle -
Ramesh Reddy