Issue Details (XML | Word | Printable)

Type: Bug Bug
Status: Closed Closed
Resolution: Fixed
Priority: Major Major
Assignee: Unassigned
Reporter: Jean-Philippe Toupin
Votes: 1
Watchers: 1

If you were logged in you would be able to see more operations.
DataNucleus Store DB4O (ARCHIVED)

Datanucleus DB4O is not compatible with DB4O 7.12

Created: 22/Dec/09 06:37 PM   Updated: 21/Apr/10 07:43 PM   Resolved: 27/Jan/10 04:36 PM
Component/s: None
Affects Version/s: 2.0.0.m1
Fix Version/s: 2.0.1

Datanucleus 2.0.0-m4
Datanucleus-Db4o 2.0.0-m3
java version "1.6.0_14"

Datastore: DB4O

 Description  « Hide
The method:


Does not exist anymore in Db4o 7.12. You cannot pass a Configuration object anymore.

Until this is fixed I suggest that the Db4o page gets updated to mention Db4o 7.4 is required.

Sort Order: Ascending order - Click to sort in descending order
Andy Jefferson added a comment - 22/Dec/09 08:37 PM
Version can't be 2.0-release since that doesn't exist.
Obviously if db40 go around changing significant API's during a minor release cycle then they will break things in dependent software - obviously the best way would be for them to maintain that plugin, but sadly they haven't grasped the opportunity so it will be unresourced for the foreseeable future. Thanks for the report.

Jean-Philippe Toupin added a comment - 22/Dec/09 09:29 PM
Completely agree with you.

I am not Db4o expert but I will check to see if I can fix the issue and submit a patch.

Carl Rosenberger added a comment - 27/Jan/10 02:45 PM
We removed the ObjectServer#openClient(Configuration configuration) method, the one that takes a configuration parameter. We wanted to make perfectly clear that the configuration is always ignored, since an ObjectServer can only run with one configuration and since embedded clients don't get their own Configuration.

It should be very straightforward to change DataNucleus to call ObjectServer#openClient() without the configuration parameter only.

Andy Jefferson added a comment - 27/Jan/10 04:36 PM