Eclipse Community Forums: EclipseLink » be able to specify JDBC driver jar w/o adding it to manifest

Help

Home

Home » Eclipse Projects » EclipseLink » be able to specify JDBC driver jar w/o adding it to manifest

Show: Today's Messages :: Show Polls :: Message Navigator

be able to specify JDBC driver jar w/o adding it to manifest [message #491935]

Fri, 16 October 2009 15:34

thomas menzel

Messages: 81
Registered: July 2009

Member

hi,

from what i understand, it is mandatory that the JDBC driver bundle either needs to be imported or required in the MANIFEST by the bundle using EL.

are there any plans to make this more dynamic? i.e. be able to specify the location of the driver via properties, such there is no need for a user to change the manifest if he chooses to use another JDBC driver/database?

is there a bug/enhancement for this already? i'd be happy to vote on it Wink

thomas menzel aka tom

Report message to a moderator

Re: be able to specify JDBC driver jar w/o adding it to manifest [message #492234 is a reply to message #491935]

Mon, 19 October 2009 14:35

James Sutherland

Messages: 1939
Registered: July 2009
Location: Ottawa, Canada

Senior Member

The issue is that the way JDBC is normally used does not really function in an OSGi environment. I think there is some discussion in the OSGi community to define how JDBC should work, such as an OSGi service. In the man time, I'm not sure there is much EclipseLink can do to address this on its own.

James : Wiki : Book : Blog : Twitter

Report message to a moderator