we're currently switching to a new DataNucleus ( http://www.datanucleus.org ) in the JFire development branch (trunk, 1.1). I just committed DataNucleus 2.1.0-m2-SNAPSHOT built 2010-04-21.
Of course, the stable branch of JFire 1.0 continues using DataNucleus 1.1.3.
We're still doing some final testing and fine-tuning of the new configuration files. We'll post news here as soon the work is done - along with some information of what you need to do.
Best regards, Marco :-)
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
JFire trunk is now using DataNucleus 2.1.0-m3-SNAPSHOT built on 2010-04-29. It's working fine with MySQL and Derby. Derby required some special treatment and thus bugfixes/workarounds in DataNucleus:
Note, that using JFire with Derby in a 64-bit JVM requires quite a lot of memory - the default of 1GB is insufficient - I usually set the heap size to 2GB, but that's probably more than required.
Best regards, Marco :-)
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
DO NOT ANSWER TO THIS POST. ANSWER TO THE ORIGINAL POST INSTEAD.
Original post: https://www.jfire.org/modules/newbb/viewtopic.php?forum_id=2&topic_id=470#forumpost1662
by: Marco (marco)
on: Thu Apr 22 16:03:02 CEST 2010
Hello *,
we're currently switching to a new DataNucleus ( http://www.datanucleus.org ) in the JFire development branch (trunk, 1.1). I just committed DataNucleus 2.1.0-m2-SNAPSHOT built 2010-04-21.
Of course, the stable branch of JFire 1.0 continues using DataNucleus 1.1.3.
We're still doing some final testing and fine-tuning of the new configuration files. We'll post news here as soon the work is done - along with some information of what you need to do.
Best regards, Marco :-)
DO NOT ANSWER TO THIS POST. ANSWER TO THE ORIGINAL POST INSTEAD.
Original post: https://www.jfire.org/modules/newbb/viewtopic.php?forum_id=2&topic_id=470#forumpost1678
by: Marco (marco)
on: Sat May 01 00:37:38 CEST 2010
Hello *,
JFire trunk is now using DataNucleus 2.1.0-m3-SNAPSHOT built on 2010-04-29. It's working fine with MySQL and Derby. Derby required some special treatment and thus bugfixes/workarounds in DataNucleus:
http://www.datanucleus.org/servlet/jira/browse/NUCRDBMS-379
http://www.datanucleus.org/servlet/jira/browse/NUCRDBMS-377
http://www.datanucleus.org/servlet/jira/browse/NUCRDBMS-376
Note, that using JFire with Derby in a 64-bit JVM requires quite a lot of memory - the default of 1GB is insufficient - I usually set the heap size to 2GB, but that's probably more than required.
Best regards, Marco :-)