[teiid-dev] Admin API Methods

[Ramesh Reddy]

On Tue, 2009-11-03 at 12:05 -0500, Ken Johnson wrote:
> Won't the data source connections be specific to Teiid since the
> Teiid 
> semantics (capabilities, metadata) won't be applicable to non-Teiid 
> apps? 
For the JDBC Connectors, the data source and connector parts are defined
in separate JCA entities. One would be Teiid specific and another is
generic to the container. Teiid connector internally looks up and uses
the JCA data source as its physical connection to the source.

>  Also, regardless of the underlying operation used to 
> control/stop/start, it would be useful for the API to provide a 
> wrapper.  The user still may be able to control through generic 
> container mechanisms, but the Teiid administrator should have a 
> consistent API into all the moving parts of a Teiid system even if
> they 
> are "standard" and accessible through other means.  They should not
> have 
> to context switch (and tool switch) when administering different
> system 
> components.  I suggest this applies to the admin API as well as admin 
> console.
This is where the your argument about Teiid based identity comes into
picture. Yes, I am looking into providing those hooks. This may span
into new API methods as I was eluding to in the previous email. I will
post what they may be in coming days.