Hi all,
as far as I remember
the fact that the database drivers are part of the manifest is that the elcipseLink/JPA
version we use in SMILA does not support loading of arbitrary database drivers
, yet. Everything is configurable, but the actual classloading is not solved.
This issue should be taken care of in newer releases. So we should check them
out.
The second issue can
also be directly solved using eclipseLink/JPA functionality. Instead of having
the annotations in the code (Java classes) it’s possible to provide them
using an XML configuration file. Someone has to figure out how this is used,
especially in an OSGi environment.
Bye,
Daniel
Von: smila-dev-bounces@xxxxxxxxxxx
[mailto:smila-dev-bounces@xxxxxxxxxxx] Im Auftrag von Thomas Menzel
Gesendet: Donnerstag, 8. Oktober 2009 06:36
An: Weber, Andreas, M-ED
Cc: Smila project developer mailing list
Betreff: [smila-dev] 2 new bugs regarding storages and JPA
Hi anderas,
since i know that you have integrated SQL
Server as well into smila you will, no doubted , come accross these 2 issues
that I just posted:
https://bugs.eclipse.org/bugs/show_bug.cgi?id=291732
https://bugs.eclipse.org/bugs/show_bug.cgi?id=291733
did you implement a solution for these on
the way?
Or found some useful information how these
can be fixed?
If so, plz post at those issues.
@ all
IMO we don’t need a wiki page
to discuss these items, or?
Kind regards
Thomas Menzel @ brox IT-Solutions GmbH