Cannot persist entities to Stardog with Empire and Spring declaritive transaction management due to StardogException: A transaction is already open exception about empire HOT 3 OPEN

At a glance, I suspect this is related to the todo in that code, specifically, needing to be able to join a current transaction.

That's pretty straightforward to add, probably only needs to be added to SupportsTransactions. But I've never tested Empire with Spring, so there might be other issues you'll hit given that Empire isn't fully JPA-compliant.

from empire.

Thanks for taking a look. We're going ahead with Empire provisionally to see how it works for us. I'll let you know if I run into any other issues using it with Spring.

from empire.

Sure.

If you're using Empire mostly for the Java Bean to/from RDF capabilities, or you run into other Spring JPA incompatibilities, the rendering engine of Empire was cleaned up and released separately as Pinto, and could be an option for you.

The upside would be it doesn't do anything for transactions, so you can control them yourself and get exactly the behavior you want. The downside is that it doesnt do anything for transactions so you have to control them yourself.

I'm going to move Empire to using Pinto internally (#99) which will simplify moving between just bean serialization and the more heavyweight JPA support.

from empire.