Tore,
I agree with you - just using the jdbc-odbc bridge and possibly an ORM
layer (certainly a DAO layer of some sort - at minimum SpringJDBC) is a
better approach. Less middleware....
I hadn't heard of Cayenne - I'll have to check it out. How does it
compare to Hibernate?
Martin
Tore Halset wrote:
Why not use the odbc/jdbc bridge from your java application to MS
Access? With a decent ORM, you will be able to switch out Access with
MySQL at a later stage without any change to your java code. Apache
Cayenne is working with MS Access (using a contrib adapter), and
almost any other RDBMS. It also has a dataport utility that can be
used to copy your data from MS Access to to MySQL. Cayenne comes with
example code to map WKT or WKB in your database to JTS Geometries on
the java side.
http://cayenne.apache.org/
http://cwiki.apache.org/confluence/display/CAY/Mapping+JTS+Geometries
JEQL looks like a really cool alternative for operating on files, but
converting a real database to files to use JEQL does not sound like a
good use case for JEQL. Or is it?
Regards,
- Tore, using PostgreSQL, cayenne and JTS.
_______________________________________________
jts-devel mailing list
jts-devel@lists.jump-project.org
http://lists.refractions.net/mailman/listinfo/jts-devel
--
Martin Davis
Senior Technical Architect
Refractions Research, Inc.
(250) 383-3022
_______________________________________________
jts-devel mailing list
jts-devel@lists.jump-project.org
http://lists.refractions.net/mailman/listinfo/jts-devel
