[
https://issues.jboss.org/browse/TEIID-1352?page=com.atlassian.jira.plugin...
]
Steven Hawkins commented on TEIID-1352:
---------------------------------------
There is a deep dependency between Teiid/Teiid Designer for parsing/resolving/validation.
Breaking the fundamental dependency on the Teiid language objects is desirable for Teiid,
but at this point would just fork AST/langauge object/parsing responsibilities over to
Designer. Resolving and validation could be handled through sql text based interfaces,
but resolving especially should probably also fork so that Designer could be more flexible
(line by line/incremental resolving, collecting errors rather than throwing an exception
immediately, etc.) It has been our view that we gain so little in the near term by
performing this fork and it introduce overhead in keeping both code bases in synch as the
language evolves that Teiid Designer is not well equipped to absorb.
Just separating out the validation dependency (via a sql text based mechanism) while
leaving the language object dependency would not make any sense.
Produce Admin API jar containing only Interfaces.
-------------------------------------------------
Key: TEIID-1352
URL:
https://issues.jboss.org/browse/TEIID-1352
Project: Teiid
Issue Type: Feature Request
Components: AdminApi
Reporter: John Doyle
Assignee: Steven Hawkins
TEIIDDES-175 requires the creation of a target runtime for Teiid so that the tooling can
be further abstracted from changes in Teiid. In order to accomplish this the tooling
requires an Admin API jar containing only interfaces. The Designer code that depends upon
the Admin API could be compiled with this jar, and the plug-in defining the target runtime
would load the implementation of the Admin API at runtime.
--
This message is automatically generated by JIRA.
For more information on JIRA, see:
http://www.atlassian.com/software/jira