The mapping to the profile service is outside of Teiid. I hope your
not suggesting that adminapi have a dependency on the profile service.
On Nov 3, 2009, at 8:30 AM, Ramesh Reddy wrote:
Van,
Since lot of work is still pending let's not finalize the list of the
methods to keep just yet. In next couple weeks this will become more
clear. We know few of the methods that are definitely being removed
like
extensions, process, log, configuration etc. I think you are right
about
the transactions method, this is one from to keep pile.
Per discussion on the previous thread to keep the identity of the
Connectors in Teiid, we still need to keep the Connector binding
specific calls.
> setConnectorBindingProperty
> addConnectorBinding
> deleteConnectorBinding
> exportConnectorBinding
> getConnectorBindings
> startConnectorBinding
> stopConnectorBinding
I would suggest you start with these to start mapping them to the
profile service. Note
that supporting the previous file formats is not necessary, they
should be same as the container's.
Additionally Teiid also needs a method like
"getConnectorPropertyDefinitions" which will describe the properties
defined inside the "ra.xml" file,
to be used with tools like designer to define their UI.
Next we will tackle monitoring, then on to VDB specific methods.
Ramesh..
_______________________________________________
teiid-dev mailing list
teiid-dev(a)lists.jboss.org
https://lists.jboss.org/mailman/listinfo/teiid-dev
Van Halbert
Principal Software Eng.
Red Hat, Inc.
------
vhalbert(a)redhat.com