Some Eclipse Foundation services are deprecated, or will be soon. Please ensure you've read this important communication.

Bug 369029

Summary: Support JPA access to NoSQL databases
Product: [RT] Gemini.JPA Reporter: Gunnar Wagenknecht <gunnar>
Component: CoreAssignee: Michael Keith <michael.keith>
Status: RESOLVED FIXED QA Contact:
Severity: normal    
Priority: P3    
Version: 1.0.0   
Target Milestone: 1.1.0 M2   
Hardware: All   
OS: All   
Whiteboard:
Attachments:
Description Flags
patch for Gemini JPA none

Description Gunnar Wagenknecht CLA 2012-01-19 03:15:19 EST 
Created attachment 209726 [details]
patch for Gemini JPA

In bug 366426 the EclipseLink team is working on implementing JPA support for NoSQL databases. With a few little modifications I was able to get it running with Gemini JPA. 

Gemini JPA basically needs a way to ignore data source handling in order to not try to acquire a data source. EclipseLink allows to explicitly turn off data source handling by setting it to an empty string. That logic also works with Gemini JPA. However, I wonder if there is a better way to detect situations when a data source is actually required.
Comment 1 Michael Keith CLA 2012-05-23 13:30:19 EDT 
One approach could be to create an OSGi spec for resource adapter services. This would provide proper dependency support. Did you work out the dependencies from EclipseLink to MongoDB or did you just connect to a MongoDB instance using the host/port, etc, running exernally?
Comment 2 Gunnar Wagenknecht CLA 2012-05-23 13:44:37 EDT 
For the beginning it's sufficient if the actual dependencies aren't managed within JPA. So basically one just passes host/port configuration information within the properties or a MongoDB connection object. EclipseLink supports both.
Comment 3 Michael Keith CLA 2012-05-28 12:19:19 EDT 
Added support for a new property. 
See http://wiki.eclipse.org/Gemini/JPA/Documentation/OtherTopics#Non-relational_Databases for information on how to enable this feature.