Ok, this has been solved. As suspected, it had to do with the fact that there was another application context being loaded that was not included in my Eclipse project after I converted it from the old STS to the new one.
Everything is back to normal, now. I can get back to exploring SDN 3.0.1! Hooray! Thanks, all. On Thursday, March 20, 2014 2:41:22 PM UTC-4, BtySgtMajor wrote: > > Ok, I'm not having much luck with this. I've verified the base-package > attribute is set for both those elements, and I've even tried changing the > order of them in my application context (not that I expected that to really > matter). > > What else could it be? The POJO in question inherits from a @NodeEntity, > but I don't think that would produce the exception I'm seeing. > > Here's what I have for the two config lines in question: > > <neo4j:repositories base-package="com.proj.vonneumanns.repositories"/> > ... > <neo4j:config graphDatabaseService="graphDatabaseService" > base-package="com.proj.vonneumanns.entities" /> > > > Any other thoughts/ideas? Sorry to be daft about this. :) > > On Wednesday, March 19, 2014 6:23:19 PM UTC-4, Mike Holdsworth wrote: >> >> Yes; it worked with that single configuration change. However next I hit >> deployment problems with the model objects. Once I removed the name in the >> @Indexed, it deployed cleanly. >> >> >> >> -- You received this message because you are subscribed to the Google Groups "Neo4j" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. For more options, visit https://groups.google.com/d/optout.
