Hi Thomas, > It sounds wrong to add an OSGi _interface_ directly to the H2 jar
As mentioned, you always can use dynamic imports but have to live with the fact of a class not found exception when loading the class. As an alternative, you can always supply a seperate bundle with a static import which just import the JDBC service as well as the h2 bundle. Thats the way I implemented the MySQL Wrapper ans should be considered as the best practise from the OSGi point of view, some peaple just don't like havin another bundle where in fact is no problem with that at all. > This all sounds quite complicated, and easy to get wrong. Its not that complicated at all. If you need any help with that let me know, be the first database to support OSGi JDBC service nativly ;) -- 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.
