[teiid-issues] [JBoss JIRA] (TEIID-2062) Produce an embeddable Teiid engine

[Steven Hawkins (JIRA)]

    [ https://issues.jboss.org/browse/TEIID-2062?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12700159#comment-12700159 ] 

Steven Hawkins commented on TEIID-2062:
---------------------------------------

My initial approach is to refactor the FakeServer into a class usable from the runtime module.  We would keep several simplifications from the FakeServer, such as a single shared ConnectorManagerRepository (rather than VDB scoping), limited configurablity, and no socket transports by default.  For now I am leaving out a default system vdb, although that would be easy to add.  VDB deployment is target at dynamic scenarios, see EmbeddedServer.deployVDB, and ExectionFactories are expected to be manually added via EmbeddedServer.addTranslator

Enhancements include:
-a named connection factory lookup override (EmbeddedServer.addConnectionFactoryProvider) rather than just relying on the default JNDI strategy.
-switching the engine thread pool to a WorkManager based implementation, which allows for context propagation without setting a SecurityHelper.

Issues include:
-Some functionality may be needed from jboss integration.  Replication requires setting an ObjectReplicator, which is too complicated to expect alternative implementations.  Also resultset caching key distribution could be done using infinispan, rather than replication.
                
> Produce an embeddable Teiid engine
> ----------------------------------
>
>                 Key: TEIID-2062
>                 URL: https://issues.jboss.org/browse/TEIID-2062
>             Project: Teiid
>          Issue Type: Enhancement
>          Components: Embedded
>            Reporter: Steven Hawkins
>            Assignee: Steven Hawkins
>             Fix For: 8.1
>
>
> Teiid's federation and query processing features are of use to several other projects.  An embeddedable form is desired such that:
> - the application server is not required
> - queries could be issued in the engine object model to by-pass parsing/validation and results retrieved without the need for JDBC
> - new translators could be added
> The following would be open for discussion:
> - the inclusion of saxon/xom/nux for SQL/XML processing
> - if the general deployment logic would be needed, or if just a single dynamic vdb is all that is needed
> See the org.teiid.jdbc.FakeServer in the test-integration/common module for a rough approximation at the entry point for a embeddable server.  Note that it is more geared at unit testing JDBC/ODBC rather than providing the features needed here.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira