Hi Thibaut, we currently have a working solution that changes the commitCows() call from a during commit call to an afterCompletion synchronization. It seems to work fine and your test case passes. Essentially it roots out the implicit assumption in that part of the kernel that he transaction should be available during the commit. There is a code freeze in place however in preparation for the upcoming milestone release, so you could either wait for the release after that or clone the source shortly after, probably late this week.
hope that helps, CG On Tue, Oct 11, 2011 at 8:01 AM, tcolar <[email protected]> wrote: > Hi Chris. > I don't mean to pressure, I write OSS myself and I know time is > available whenever it is, so i just have some quick questions about this > issue. > > Basically I just need to decided whether to shelf this feature of our > project for now or if i can get any idea on how much work / how long it > would take to get it working. > > 1) Do you think it's an issue with atomikos itself and I should I bring > the issue to them ? > 2) Is that something that would be fixed in neo4j itself, if so do you > have any rough estimates ? > 3) Is there some sort of workaround you could think of that I could > implement ? > > Any other suggestions or ammount of work/time needed would be appreciated. > > Thanks. > > > -- > View this message in context: > http://neo4j-community-discussions.438527.n3.nabble.com/Trying-to-use-Neo4J-with-Atomikos-transaction-manager-issues-with-Lucene-index-tp3400319p3411656.html > Sent from the Neo4j Community Discussions mailing list archive at Nabble.com. > _______________________________________________ > Neo4j mailing list > [email protected] > https://lists.neo4j.org/mailman/listinfo/user > _______________________________________________ Neo4j mailing list [email protected] https://lists.neo4j.org/mailman/listinfo/user
