Some Eclipse Foundation services are deprecated, or will be soon. Please ensure you've read this important communication.
Bug 339688 - [JPA] investigate better JPA integration w/o bundle coupling
Summary: [JPA] investigate better JPA integration w/o bundle coupling
Status: NEW
Alias: None
Product: z_Archived
Classification: Eclipse Foundation
Component: Smila (show other bugs)
Version: unspecified   Edit
Hardware: All All
: P3 enhancement (vote)
Target Milestone: ---   Edit
Assignee: Project Inbox CLA
QA Contact:
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2011-03-11 08:42 EST by thomas menzel CLA
Modified: 2022-07-07 11:31 EDT (History)
0 users

See Also:

Attachments
Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.
Description thomas menzel CLA 2011-03-11 08:42:18 EST 
i have stumbled across this video http://www.youtube.com/watch?v=X9WWCxQwXME that explains how one does proper JPA+OSGi development thru a service.

i dont think we do this, but dont know for sure. so i created this issue to keep track of this and keep it in the pipeline, as i have no time to follow up on this ATM.

what i dont know is also, if thru that the JDBC driver problem is addressed either (ATM we need to import/require the bundle that hosts the driver and IMO the JPA impl/provider (EL in our case) should just need to know about this and not each JPA impl'ing bundle)