jlowenz / hypergraphdb

Automatically exported from code.google.com/p/hypergraphdb
0 stars 0 forks source link

bje build problem - linkBinding.objectToEntry / linkBinding.objectToEntry #82

Closed GoogleCodeExporter closed 9 years ago

GoogleCodeExporter commented 9 years ago
What steps will reproduce the problem?
When importing hypergraphDB 1.2 beta in intellij, building fails with two very 
closely related errors. I have seen this linkbinding error several times in the 
past and if I remember correctly, i worked around it by disabling either bje or 
bdb.

What is the expected output? What do you see instead?
BJEStorageImplementation.java 234,20:
error: no suitable method found for 
objectToEntry(HGPersistentHandle[],com.sleepycat.je.DatabaseEntry)
method LinkBinding.objectToEntry(HGPersistentHandle[],TupleOutput) is not 
applicable
(actual argument com.sleepycat.je.DatabaseEntry cannot be converted to 
TupleOutput by method invocation conversion)
method 
TupleBinding.objectToEntry(HGPersistentHandle[],com.sleepycat.db.DatabaseEntry) 
is not applicable
(actual argument com.sleepycat.je.DatabaseEntry cannot be converted to 
com.sleepycat.db.DatabaseEntry by method invocation conversion)

und 

error: no suitable method found for 
entryToObject(com.sleepycat.je.DatabaseEntry)
method LinkBinding.entryToObject(TupleInput) is not applicable
(actual argument com.sleepycat.je.DatabaseEntry cannot be converted to 
TupleInput by method invocation conversion)
method TupleBinding.entryToObject(com.sleepycat.db.DatabaseEntry) is not 
applicable
(actual argument com.sleepycat.je.DatabaseEntry cannot be converted to 
com.sleepycat.db.DatabaseEntry by method invocation conversion)

Original issue reported on code.google.com by Ingvar.Bogdahn on 4 Jul 2012 at 8:54

GoogleCodeExporter commented 9 years ago
That happens when both db.jar and je.jar are included in the same classpath. It 
must be one or the other. This is because both implementations use the same 
package and class names. Unfortunately, there's no way around this and it's not 
a HGDB problem.

Original comment by borislav...@gmail.com on 5 Jul 2012 at 1:36