Hi Thomas, > I wonder if it would cause no problems > for OSGiframeworks that don't support this specification.
The best option for this is to integrate the JDBC Service interface into the bundle (if you can live with the OSGi licence requirements for this) which can be downloaded on the specifikation page under the "Enterprise Specification" section, export the package as well as add it as an imported package with resolution:=optional. So two cases can apply: 1) The OSGi Framework support the JDBC Service: Your driver will import the package from the framework 2) The OSGi Framework does -NOT- support the JDBC Service: The fallback interface of your internal interface will be used and your drive becomes the "implementation" of the JDBC service (note: In fact the JDBC service does not involve any implementation, just providing the interface, thats why i quoted the 'implementation'. I don't know why not every OSGi framework includes the JDBC service since there is nearly no effort for including it) Alternativly, you can just import with resolution:=optional, and just guard your service registration code this way that it silently fails when the interface can't be loaded at runtime. If you want to learn more about that I can forward you to the OSGi core specifiaction part 3.6.3 Optional Packages. -- You received this message because you are subscribed to the Google Groups "H2 Database" group. To post to this group, send email to [email protected]. To unsubscribe from this group, send email to [email protected]. For more options, visit this group at http://groups.google.com/group/h2-database?hl=en.
