Mmh,
the question is if at least the exceptions and the TX abstract classes could
be moved into exported packages. Still, instantiating implementation classes
in the templates is probably the root of the problems. But then, as with
pointing out implementations through the Java Service notion,
Peter,
The classes that Martin Hunger listed are the offending ones.
Best regards,
Jean-Pierre
2011/5/23 Peter Neubauer peter.neuba...@neotechnology.com:
Jean-Pierre,
do you know which classes exactly are the offending ones in neo4j *impl?
Would like to know in order to either avoid suing
I have not spent much more time trying to get SDG running as a bundle
any more. I'll give it another shot today or tomorrow and let you know
how I'm proceeding.
What definitively has to be done is fixing the package imports of SDG
and the package exports of neo4j (see
What we are currently using inside of SDG are:
* TX/XA-Manager Implementations and Providers
org.springframework.data.graph.neo4j.config (2 usages)
Neo4jConfiguration.java (2 usages)
(23: 24) import
Jean-Pierre,
do you know which classes exactly are the offending ones in neo4j *impl?
Would like to know in order to either avoid suing them or move them into the
API.
Cheers,
/peter neubauer
GTalk: neubauer.peter
Skype peter.neubauer
Phone +46 704 106975
LinkedIn
Hi there,
any solution to this or do we need to dig deeper here?
Cheers,
/peter neubauer
GTalk: neubauer.peter
Skype peter.neubauer
Phone +46 704 106975
LinkedIn http://www.linkedin.com/in/neubauer
Twitter http://twitter.com/peterneubauer
http://www.neo4j.org
This could be the problem, yes. The repository factories that create
the repositories from the interface definitions would need to import
the domain specific packages that contain the interfaces to have
access to them - which requires buddy loading.
It seems as if the CGLIB enhanced class
In OSGi, missing classes can be down to which bundles are visible to
the bundle doing the scanning. In this case, whatever is doing the
classpath scanning cannot see the bundle exporting your domain package.
From a number of years back, I remember having to use
eclipse-registerbuddy to
Hi,
I've written an article [1] showing how to run neo4j embedded database
inside an OSGi container. Starting from that I think you can create a bundle
which uses this database to create the appropriate Spring data
configuration. I suppose that spring-data-graph is packaged as a OSGi
compatible
Well, at the minimum, it's only a question of adding some extra headers
(Bundle-Symbolic, Export-Package; ...) in the package MANIFEST and this can
be done automatically using the maven-bundle-plugin.
You can have a look at Neo4j pom file or this second article :
SDG is using bundlor to generate the MANIFEST.MF file.I already fixed
the MANIFEST and the spring data neo4j bundle can now be resolved.
But when the spring application context is loaded, the class
org.springframework.data.graph.neo4j.config.Neo4jConfiguration
cannot be found during bean
Forwarded it to the AJ project lead Andy Clement, he knows this OSGi + AJ stuff
certainly better than me :)
Cheers
Michael
Am 13.05.2011 um 14:03 schrieb Jean-Pierre Bergamin:
SDG is using bundlor to generate the MANIFEST.MF file.I already fixed
the MANIFEST and the spring data neo4j bundle
12 matches
Mail list logo
