Hi folks,
i just committed the
last change in regard to this bug:
[storages] JPA :: allow for custom
definition in config what data types are used :: switch all to orm.xml @ https://bugs.eclipse.org/bugs/show_bug.cgi?id=291733#c4
tests in eclipse run
thru and no semantic changes have been made, except in some test bundles.
Kind regards
Thomas Menzel @ brox IT-Solutions GmbH
From: smila-dev-bounces@xxxxxxxxxxx
[mailto:smila-dev-bounces@xxxxxxxxxxx] On Behalf Of Thomas Menzel
Sent: Montag, 12. Oktober 2009 10:14
To: Smila project developer mailing list
Subject: RE: [smila-dev] 2 new bugs regarding storages and JPA
Hi,
i just updated:
291733: [storages]
JPA :: allow for custom definition in config what data types are used
https://bugs.eclipse.org/bugs/show_bug.cgi?id=291733
it is all not so easy
and i outlined 2 ways we could go, actually we could even provide both
alternatives depending on how much the user wants to change and in the first
alternative he doesn’t need to know any JPA, which is an advantage IMO.
If you have time plz
feel free to comment.
Going to POC them in
the next 2 days
Kind regards
Thomas Menzel @ brox IT-Solutions GmbH
From: smila-dev-bounces@xxxxxxxxxxx
[mailto:smila-dev-bounces@xxxxxxxxxxx] On Behalf Of Thomas Menzel
Sent: Donnerstag, 8. Oktober 2009 21:09
To: Smila project developer mailing list
Subject: RE: [smila-dev] 2 new bugs regarding storages and JPA
Hi Daniel,
Thx for the info in
regard to EL. Going to ask them what the status is on that.
Regarding the
metadata: I'm getting myself smart already on JPA.
Kind regards
Thomas Menzel @ brox IT-Solutions GmbH
From: smila-dev-bounces@xxxxxxxxxxx
[mailto:smila-dev-bounces@xxxxxxxxxxx] On Behalf Of Daniel.Stucky@xxxxxxxxxxx
Sent: Donnerstag, 8. Oktober 2009 18:10
To: smila-dev@xxxxxxxxxxx
Subject: AW: [smila-dev] 2 new bugs regarding storages and JPA
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
No
virus found in this incoming message.
Checked by AVG - www.avg.com
Version: 8.5.421 / Virus Database: 270.14.7/2421 - Release Date: 10/07/09
20:49:00
No
virus found in this incoming message.
Checked by AVG - www.avg.com
Version: 8.5.421 / Virus Database: 270.14.7/2421 - Release Date: 10/08/09
06:39:00
No virus
found in this incoming message.
Checked by AVG - www.avg.com
Version: 8.5.421 / Virus Database: 270.14.7/2422 - Release Date: 10/11/09
06:39:00