On Wed, 25 Feb 2009, Andi Vajda wrote:
On Wed, 25 Feb 2009, Bill Janssen wrote:
Bill Janssen <jans...@parc.com> wrote:
I'm trying to wrap neo4j (http://neo4j.org/) with JCC (2.1, the latest
checkout from
Subversion).
I can't; it fails on org.neo4j.impl.core.RelationshipType
(http://api.neo4j.org/current/org/neo4j/api/core/RelationshipType.html):
This looks like a JCC bug to me. There are two interfaces in that
package, "Relationship", and "RelationshipType". I think it's
auto-generating a Python type called "RelationshipType" as part of the
definition of "Relationship", and that conflicts with the header file
for the Java interface "RelationshipType".
Indeed, there is a clash between JCC's suffixing things it generates with
'Type' and that class name. JCC should use something more rare, such as
'__Type', for example, or, better yet, allow a parameter to specify the
suffix. At least, it should be less hardcoded than now.
While the fix is relatively easy to implement, it requires a lot of edits.
I should have something tomorrow.
I changed the 'Type' suffix used to name Python types to '$$Type'.
neo4j now lets itself be wrapped. Fixed in rev 748053.
Andi..
