[
https://issues.jboss.org/browse/TEIID-2011?page=com.atlassian.jira.plugin...
]
Ramesh Reddy commented on TEIID-2011:
-------------------------------------
Added initial implementation that does select, updates and very premature [wrong] insert
functionality. Tested with standard JPA interface.
When tried to configure the alternative JPA provider to use Hibernate OGM in AS7, there
were few issues and I never could complete the task. There is not much documentation with
OGM on AS7. Also there is no activity on this project from last few months. So, need
further investigation.
For testing used sakila DB from MySQL [
http://downloads.mysql.com/docs/sakila-db.zip]
- reverse engineered the model using the JBDS
- gave a JNDI name, and deployed in the AS7
Used the JNDI name of the Persistence Unit as the "connection-jndi-name" in the
vdb.xml with "jpa2" translator. Example JAR and VDB attached.
Develope a JPA Translator
-------------------------
Key: TEIID-2011
URL:
https://issues.jboss.org/browse/TEIID-2011
Project: Teiid
Issue Type: Feature Request
Components: Misc. Connectors
Reporter: Ramesh Reddy
Assignee: Ramesh Reddy
Fix For: 8.1
Provide a JPA based translator in Teiid. The main driving force for this is to support
Hibernate OGM, which in turn uses big data stores like infinispan, EhCache as backing
stores. Hibernate OGM also looking to expanding to other stores like Cassendra, MongoDB
etc.
By providing JPA translator (think reverse hibernate), which provides
- Metadata
- Query API (JPQL)
which makes much easier for Teiid to identify data in big data stores and gives ways to
integrate with other kinds of sources, both relational and non-relational. This usecase is
limited to users who has defined their data using JPA and would like to use big data
stores. Additional benefit of this is to provides full Relational access to a JPA store
with JDBC/ODBC and SQL.
if the data in big data store is not in JPA objects, then see
https://issues.jboss.org/browse/TEIID-1992
--
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